# com.webmcp-tool/agent-readiness (remote · webmcp-tool.com)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `webmcp-tool.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-webmcp-tool-agent-readiness/api-mcp.md), [page](https://verifymcp.io/servers/com-webmcp-tool-agent-readiness/api-mcp)

## Channel facts

- Endpoint: `https://webmcp-tool.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 445 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-webmcp-tool-agent-readiness 'https://webmcp-tool.com/api/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-webmcp-tool-agent-readiness]
url = "https://webmcp-tool.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-webmcp-tool-agent-readiness": {
      "type": "remote",
      "url": "https://webmcp-tool.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-webmcp-tool-agent-readiness --url 'https://webmcp-tool.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-webmcp-tool-agent-readiness:
    url: "https://webmcp-tool.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-webmcp-tool-agent-readiness": {
      "Transport": "http",
      "Url": "https://webmcp-tool.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-webmcp-tool-agent-readiness -t streamable-http -u 'https://webmcp-tool.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 78, +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.

### 2026-09-21 (score 77, +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.

### 2026-09-19 (score 76, +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.

### 2026-09-16 (score 75, +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.

### 2026-09-14 (score 74, +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.

### 2026-09-12 (score 73, +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.

### 2026-09-10 (score 72, +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.

### 2026-09-09 (score 71, +1)

- [security regression] A breaking change shipped without a version bump: still 0.2.0
- [security regression] Tool “get_agent_stats” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 105 → 89

## MCP tools (5)

### `score_site` (~75 tokens)

Score a site for agent readiness

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.

Input parameters:

- `url` (string, required): Public http(s) address, for example example.com

Output parameters:

- `axes` (array)
- `excluded` (array)
- `fetchedAt` (string): ISO 8601
- `fixFirst` (array)
- `grade` (string)
- `host` (string)
- `methodology` (string)
- `pillars` (array)
- `reportUrl` (string)
- `score` (integer)
- `url` (string)

### `explain_check` (~70 tokens)

Explain one check

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.

Input parameters:

- `checkId` (string, required): Check identifier, for example content-without-javascript

Output parameters:

- `conditional` (boolean)
- `docs` (array)
- `fix` (string)
- `id` (string)
- `pillar` (string)
- `points` (number)
- `question` (string)
- `snippet` (string)
- `title` (string)
- `why` (string)

### `list_checks` (~38 tokens)

List the rule set

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.

Output parameters:

- `pillars` (array)

### `get_badge_embed` (~88 tokens)

Get the badge embed

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.

Input parameters:

- `url` (string, required): Public http(s) address, for example example.com

Output parameters:

- `badgePage` (string)
- `eligible` (boolean)
- `fixFirst` (array)
- `grade` (string)
- `host` (string)
- `html` (string)
- `note` (string)
- `reason` (string)
- `reportUrl` (string)
- `score` (integer)
- `tier` (string)
- `watchIt` (string)

### `watch_site` (~125 tokens)

Watch a site's score

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.

Input parameters:

- `email` (string, required): Address that will receive the confirmation and the alerts
- `url` (string, required): Public http(s) address or bare host, for example example.com

Output parameters:

- `email` (string)
- `host` (string)
- `message` (string)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-webmcp-tool-agent-readiness/api-mcp#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 69
- 2026-09-04: 69
- 2026-09-03: 68
- 2026-09-02: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://webmcp-tool.com/api/mcp
- Website: https://webmcp-tool.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-webmcp-tool-agent-readiness/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-webmcp-tool-agent-readiness/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-webmcp-tool-agent-readiness/api-mcp