Skip to content

The Ranking Factory site check

by therankingfactory.com · remote · no sign-in to list tools · v1.0.0 · published by com.therankingfactory

Free, no sign-in: checks a website's readiness for AI search and lists what it found.

Changes · 1
CompareRegistry entry

1 tool: 1 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http site-check https://therankingfactory.com/api/mcp/check

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • check_siteChecks one public website's readiness for AI search, free and without an account: whether AI crawlers are allowed in, whether the pages can be read without running JavaScript, the …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks one public website's readiness for AI search, free and without an account: whether AI crawlers are allowed in, whether the pages can be read without running JavaScript, the structured data, titles and descriptions, llms.txt and more - the same fetch-only check as therankingfactory.com/audit. Answers with each finding's title and tier (Blocker first), every check made with its result, and fullReport: the link where the person can have the full report, with what to do about each finding, emailed to them. It does not ask any AI engine whether the business is named or cited; that needs an account. One site per call, and a site can be checked a limited number of times a day.

    Annotations the server declares

    • title: Check a website for AI search
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http site-check https://therankingfactory.com/api/mcp/check

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__site-check__check_site"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as site-check. Review it before you use it.