Site Passport
REMOTE · SITEPASSPORT.ORG · SCANNED SEP 21
Live-checks whether a WordPress site is ready to be safely operated by AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 90 tokens (~90/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Site Passport MCP server?
Site Passport is a hosted endpoint at https://sitepassport.org/.well-known/mcp.json, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sitepassport.org
claude mcp add --transport http org-sitepassport-check-wordpress-agent-readiness 'https://sitepassport.org/.well-known/mcp.json'
{
"mcpServers": {
"org-sitepassport-check-wordpress-agent-readiness": {
"url": "https://sitepassport.org/.well-known/mcp.json"
}
}
} {
"servers": {
"org-sitepassport-check-wordpress-agent-readiness": {
"type": "http",
"url": "https://sitepassport.org/.well-known/mcp.json"
}
}
} [mcp_servers.org-sitepassport-check-wordpress-agent-readiness] url = "https://sitepassport.org/.well-known/mcp.json"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-sitepassport-check-wordpress-agent-readiness": {
"type": "remote",
"url": "https://sitepassport.org/.well-known/mcp.json",
"enabled": true
}
}
} openclaw mcp add org-sitepassport-check-wordpress-agent-readiness --url 'https://sitepassport.org/.well-known/mcp.json' --transport streamable-http
mcp_servers:
org-sitepassport-check-wordpress-agent-readiness:
url: "https://sitepassport.org/.well-known/mcp.json" {
"McpServers": {
"org-sitepassport-check-wordpress-agent-readiness": {
"Transport": "http",
"Url": "https://sitepassport.org/.well-known/mcp.json"
}
}
} assistant mcp add org-sitepassport-check-wordpress-agent-readiness -t streamable-http -u 'https://sitepassport.org/.well-known/mcp.json'
{
"mcpServers": {
"org-sitepassport-check-wordpress-agent-readiness": {
"type": "http",
"url": "https://sitepassport.org/.well-known/mcp.json"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +8
- Authorization: unverified → partial ▲ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://sitepassport.org/.well-known/mcp.json
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sitepassport.org | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3a90805a585aa78a132051490b247349 |
| SANs: sitepassport.org, *.sitepassport.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sitepassport.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| sitepassport.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; object-src 'none'; frame-src https://challenges.cloudflare.com https://www.youtube-nocookie.com; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://i.ytimg.com https://www.google-analytics.com https://www.googletagmanager.com; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sitepassport.org/.well-known/mcp.json | Verified | 200 | |
| http (plaintext) | http://sitepassport.org/.well-known/mcp.json | HTTPS enforced | 301 | https://sitepassport.org/.well-known/mcp.json |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_wordpress_agent_readiness ~90
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 self-reported.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site URL to check, e.g. https://example.com |
No output schema declared.
No examples provided.
What is the Site Passport MCP server?
Site Passport is an MCP server listed in the public MCP registry as org.sitepassport/check-wordpress-agent-readiness. Live-checks whether a WordPress site is ready to be safely operated by AI agents. This page covers its hosted endpoint (https://sitepassport.org/.well-known/mcp.json).
Is the Site Passport MCP server safe to use?
Site Passport scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Site Passport MCP server expose?
Site Passport exposes 1 tool: check_wordpress_agent_readiness. Their descriptions and schemas cost roughly 90 tokens of context every time the server is loaded.
Does the Site Passport MCP server require authentication?
No. We connected to Site Passport without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Site Passport MCP server still maintained?
Site Passport is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.