# com.webmcp-tool/agent-readiness

> Scores any public website on how usable it is by AI agents, with per-check evidence.

- name: com.webmcp-tool/agent-readiness
- version: 0.2.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 75/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.webmcp-tool%2Fagent-readiness
- tools: https://api.protogrid.dev/v1/servers/com.webmcp-tool%2Fagent-readiness/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "agent-readiness": {
      "type": "http",
      "url": "https://webmcp-tool.com/api/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-48d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 75/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 824 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 7 tool changes in 30 days
- fail `stability.rug_pull`: 2 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 824 tokens to load them all
- tool set hash: 031d881e4b3525a23f198266ae49f42f
- tools last changed: 2026-10-01T08:38:43.357Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.webmcp-tool/agent-readiness.svg)](https://protogrid.dev/servers/com.webmcp-tool/agent-readiness)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-01 `watch_site` changed (description)
  - before: Send a confirmation email for monitoring a site's Agent Readiness Score. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.
  - after: Use this only when the user explicitly asks to be emailed when a site's Agent Readiness Score changes. Sends a confirmation email for monitoring that site. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.
- 2026-10-01 `get_badge_embed` changed (description, annotations)
  - before: 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.
  - after: Use this when the user wants to show a site's Agent Readiness badge on that site. Scores the site if needed, then returns the HTML snippet for sites at grade C or better (bronze, silver or gold), or the reason and the first fixes when the site is not eligible. Returns HTML to paste; it installs nothing and runs no script.
- 2026-10-01 `list_checks` changed (description, annotations)
  - before: 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.
  - after: Use this when the user asks what the Agent Readiness Score measures or how it is calculated, rather than how one site performs. Lists every check in the rule set with its pillar, weight and question. Fetches nothing.
- 2026-10-01 `explain_check` changed (description, annotations)
  - before: 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.
  - after: Use this when the user asks what a specific Agent Readiness finding means, why it matters to AI agents or how to fix it, usually after score_site. Explains one check: what it asks, why an agent cares, how it is weighted and how to fix it, with a code snippet where one exists. Answers from the rule set only and fetches nothing.
- 2026-10-01 `score_site` changed (description, annotations) **meaning changed**
  - before: Score a public website for agent readiness. Returns a number out of 100, a grade, the fitness and adoption sub-scores, the highest-value fixes, scan time and whether the result came from cache. Use this first when asked whether a site is agent-ready or WebMCP-ready.
  - after: Use this when the user asks whether a website is ready for AI agents, agent-ready, AI-agent friendly or WebMCP-ready, or what to fix so agents can use it. Scores one public website out of 100 for agent readiness and returns a grade, the fitness and adoption sub-scores, the five highest-value fixes, the scan time and whether the result came from cache. Reads one public page plus standard discovery files (robots.txt, /.well-known endpoints, sitemaps, llms.txt) and up to ten same-origin script bundles; it never logs in, submits forms or changes the site. Results are cached for about an hour.
- 2026-09-25 `watch_site` changed (description, inputSchema) **meaning changed**
  - before: 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.
  - after: Send a confirmation email for monitoring a site's Agent Readiness Score. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.
- 2026-09-25 `score_site` changed (description, outputSchema)
  - before: 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.
  - after: Score a public website for agent readiness. Returns a number out of 100, a grade, the fitness and adoption sub-scores, the highest-value fixes, scan time and whether the result came from cache. Use this first when asked whether a site is agent-ready or WebMCP-ready.

Full history: https://api.protogrid.dev/v1/servers/com.webmcp-tool%2Fagent-readiness/changes

## Remotes

- https://webmcp-tool.com/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `explain_check`: Use this when the user asks what a specific Agent Readiness finding means, why it matters to AI agents or how to fix it, usually after score_site. Explains one check: what it asks, why an agent cares, how it is weighted and how to fix it, with a code snippet where one exists. Answers from the rule set only and fetches nothing.
- `get_badge_embed`: Use this when the user wants to show a site's Agent Readiness badge on that site. Scores the site if needed, then returns the HTML snippet for sites at grade C or better (bronze, silver or gold), or the reason and the first fixes when the site is not eligible. Returns HTML to paste; it installs nothing and runs no script.
- `list_checks`: Use this when the user asks what the Agent Readiness Score measures or how it is calculated, rather than how one site performs. Lists every check in the rule set with its pillar, weight and question. Fetches nothing.
- `score_site`: Use this when the user asks whether a website is ready for AI agents, agent-ready, AI-agent friendly or WebMCP-ready, or what to fix so agents can use it. Scores one public website out of 100 for agent readiness and returns a grade, the fitness and adoption sub-scores, the five highest-value fixes, the scan time and whether the result came from cache. Reads one public page plus standard discovery files (robots.txt, /.well-known endpoints, sitemaps, llms.txt) and up to ten same-origin script bundles; it never logs in, submits forms or changes the site. Results are cached for about an hour.
- `watch_site`: Use this only when the user explicitly asks to be emailed when a site's Agent Readiness Score changes. Sends a confirmation email for monitoring that site. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.