com.webmcp-tool/agent-readiness
REMOTE · WEBMCP-TOOL.COM · SCANNED SEP 24
Scores any public website on how usable it is by AI agents, with per-check evidence.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 445 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.webmcp-tool/agent-readiness MCP server?
com.webmcp-tool/agent-readiness is a hosted endpoint at https://webmcp-tool.com/api/mcp, 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 · webmcp-tool.com
claude mcp add --transport http com-webmcp-tool-agent-readiness 'https://webmcp-tool.com/api/mcp'
{
"mcpServers": {
"com-webmcp-tool-agent-readiness": {
"url": "https://webmcp-tool.com/api/mcp"
}
}
} {
"servers": {
"com-webmcp-tool-agent-readiness": {
"type": "http",
"url": "https://webmcp-tool.com/api/mcp"
}
}
} [mcp_servers.com-webmcp-tool-agent-readiness] url = "https://webmcp-tool.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-webmcp-tool-agent-readiness": {
"type": "remote",
"url": "https://webmcp-tool.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-webmcp-tool-agent-readiness --url 'https://webmcp-tool.com/api/mcp' --transport streamable-http
mcp_servers:
com-webmcp-tool-agent-readiness:
url: "https://webmcp-tool.com/api/mcp" {
"McpServers": {
"com-webmcp-tool-agent-readiness": {
"Transport": "http",
"Url": "https://webmcp-tool.com/api/mcp"
}
}
} assistant mcp add com-webmcp-tool-agent-readiness -t streamable-http -u 'https://webmcp-tool.com/api/mcp'
{
"mcpServers": {
"com-webmcp-tool-agent-readiness": {
"type": "http",
"url": "https://webmcp-tool.com/api/mcp"
}
}
} 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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- Tool “get_agent_stats” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 105 → 89 ▲ functional
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 24 Sept 2026 · Probed https://webmcp-tool.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=webmcp-tool.com | CN=YE1,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 64b5defe63fcb20367a42371ee11b211d21 |
| SANs: webmcp-tool.com, www.webmcp-tool.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of webmcp-tool.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| webmcp-tool.com. | 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 |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://webmcp-tool.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://webmcp-tool.com/api/mcp | HTTPS enforced | 301 | https://webmcp-tool.com/api/mcp |
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 →
explain_check Explain one check ~70
Explain one check from the Agent Readiness Score: what it asks, why an agent cares, how it is weighted, and how to fix it. Use after score_site when the user asks why a particular finding matters.
| Name | Type | Req | Description |
|---|---|---|---|
| checkId | string | yes | Check identifier, for example content-without-javascript |
| Name | Type | Req | Description |
|---|---|---|---|
| conditional | boolean | yes | – |
| docs | array | – | – |
| fix | string | yes | – |
| id | string | yes | – |
| pillar | string | – | – |
| points | number | yes | – |
| question | string | yes | – |
| snippet | string | – | – |
| title | string | yes | – |
| why | string | yes | – |
No examples provided.
get_badge_embed Get the badge embed ~88
Get the HTML snippet for a site's Agent Readiness badge, so it can be placed on that site. Sites at grade C or better earn bronze, silver or gold. Use when the user has a passing score and wants to display it. Returns HTML to paste; it installs nothing and runs no script.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) address, for example example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| badgePage | string | – | – |
| eligible | boolean | yes | – |
| fixFirst | array | – | – |
| grade | string | yes | – |
| host | string | yes | – |
| html | string | – | – |
| note | string | – | – |
| reason | string | – | – |
| reportUrl | string | – | – |
| score | integer | yes | – |
| tier | string | – | – |
| watchIt | string | – | – |
No examples provided.
list_checks List the rule set ~38
List every check in the rule set with its pillar, weight and question. Use when the user asks what is measured rather than how one site performs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| pillars | array | yes | – |
No examples provided.
score_site Score a site for agent readiness ~75
Score a public website for agent readiness. Returns a number out of 100, a grade, the fitness and adoption sub-scores, and the highest-value fixes. Use this first when asked whether a site is agent-ready or WebMCP-ready.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) address, for example example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| axes | array | yes | – |
| excluded | array | yes | – |
| fetchedAt | string | yes | ISO 8601 |
| fixFirst | array | yes | – |
| grade | string | yes | – |
| host | string | yes | – |
| methodology | string | yes | – |
| pillars | array | yes | – |
| reportUrl | string | yes | – |
| score | integer | yes | – |
| url | string | yes | – |
No examples provided.
watch_site Watch a site's score ~125
Watch a site's Agent Readiness Score. Takes the site and an email address; sends that address a confirmation email, and after opening the link and confirming on the page, the owner gets an alert whenever the score or a check verdict changes. Use when the user asks to monitor, track or be notified about a site's agent readiness. Nothing is sent without the recipient opening the link and confirming on the page.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Address that will receive the confirmation and the alerts | |
| url | string | yes | Public http(s) address or bare host, for example example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| host | string | yes | – |
| message | string | yes | – |
| status | string | yes | – |
No examples provided.
What is the com.webmcp-tool/agent-readiness MCP server?
com.webmcp-tool/agent-readiness is an MCP server listed in the public MCP registry as com.webmcp-tool/agent-readiness. Scores any public website on how usable it is by AI agents, with per-check evidence. This page covers its hosted endpoint (https://webmcp-tool.com/api/mcp).
Is the com.webmcp-tool/agent-readiness MCP server safe to use?
com.webmcp-tool/agent-readiness 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 com.webmcp-tool/agent-readiness MCP server expose?
com.webmcp-tool/agent-readiness exposes 5 tools: score_site, explain_check, list_checks, get_badge_embed, watch_site. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.
Does the com.webmcp-tool/agent-readiness MCP server require authentication?
No. We connected to com.webmcp-tool/agent-readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.webmcp-tool/agent-readiness MCP server still maintained?
com.webmcp-tool/agent-readiness is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.