Skip to content
Site Passport logo

Site Passport MCP server

Which MCP servers are Site Passport's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Site Passport

Whose server it is
  • Registry nameorg.sitepassport/check-wordpress-agent-readinessverified in the MCP registry

The registry name sits under sitepassport.org. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools1
  • Server calls itselfsitepassport
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 100 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check llms.txt and robots.txt for AI crawler access; review schema.org markup for AI agent readability.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "check llms.txt and robots.txt for AI crawler access", the likely first call is check_wordpress_agent_readiness.
  • For "review schema.org markup for AI agent readability", the likely first call is check_wordpress_agent_readiness.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer327 ms
  • Space in an agent's context≈ 117 tokensthe definitions of all its tools (1), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · check llms.txt and robots.txt for AI crawler access
  • can do · review schema.org markup for AI agent readability
  • not sure · verify a site's WebMCP manifest for declared agent tools

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers1 tools · read 2026-10-26
  • check_wordpress_agent_readiness

    Checks whether a WordPress site (or any website) is ready to be safely operated by AI agents: llms.txt, AI-crawler directives in robots.txt, schema.org markup, and a WebMCP capability manifest. Live-checked against the site itself, never…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "check-wordpress-agent-readiness": {
      "type": "http",
      "url": "https://sitepassport.org/.well-known/mcp.json"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http sitepassport https://sitepassport.org/.well-known/mcp.json

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://sitepassport.org/.well-known/mcp.json as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.