# Agent Ready (remote · agent-ready.dev)

Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.

- Trust score: 83/100 (high trust)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `agent-ready.dev`: 83/100 (this document), [markdown](https://verifymcp.io/servers/mlava-agent-ready-mcp/api-v1-mcp.md), [page](https://verifymcp.io/servers/mlava-agent-ready-mcp/api-v1-mcp)
- npm · `agent-ready-mcp`: 80/100, [markdown](https://verifymcp.io/servers/mlava-agent-ready-mcp/agent-ready-mcp.md), [page](https://verifymcp.io/servers/mlava-agent-ready-mcp/agent-ready-mcp)

## Channel facts

- Endpoint: `https://agent-ready.dev/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.2`

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

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 870 tokens (~108/item across 8 items; 3 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http mlava-agent-ready-mcp https://agent-ready.dev/api/v1/mcp
```

### Codex

```toml
[mcp_servers.mlava-agent-ready-mcp]
url = "https://agent-ready.dev/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mlava-agent-ready-mcp": {
      "type": "remote",
      "url": "https://agent-ready.dev/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mlava-agent-ready-mcp --url https://agent-ready.dev/api/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mlava-agent-ready-mcp:
    url: "https://agent-ready.dev/api/v1/mcp"
```

### Other

```json
{
  "mcpServers": {
    "mlava-agent-ready-mcp": {
      "type": "http",
      "url": "https://agent-ready.dev/api/v1/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-08-02 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 82, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

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

### 2026-07-27 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 75)

First indexed and scored.

## MCP tools (3)

### `scan_site` (~127 tokens)

Scan a site for AI agent readability

Runs the agent-ready.dev scanner against a URL and returns structured results: Vercel score, llmstxt.org score, and per-check findings with remediation hints. Scans may take up to ~60s; for larger scans the tool returns a scan id and asks you to poll with get_scan.

Input parameters:

- `pageLimit` (integer): Maximum number of pages to crawl. Defaults to your tier's per-scan page limit when omitted.
- `url` (string, required): Full URL of the site to scan, e.g. https://example.com. Must be a public http(s) address.

Output parameters:

- `accessibilityChecks`: Accessibility / layout-stability checks (A-series) run over the homepage.
- `accessibilityScore`: Accessibility / layout-stability sub-score (0–100) over the homepage WCAG checks; null when none ran. Separate from the Vercel score.
- `id` (string): The scan id.
- `llmstxtScore`: llms.txt score (0–100).
- `pagesDiscovered`: Number of pages discovered.
- `pagesScanned`: Number of pages scanned.
- `pollUrl`: Poll URL while the scan is still running.
- `protocolResults`: Agent-protocol checks (C-series) that ran — only for endpoints the site actually exposes.
- `rootUrl`: The scanned site URL.
- `shareUrl`: Path to the shareable report (/scan/<id>).
- `status` (string): Scan status: running, completed, or failed.
- `vercelRating`: Rating band for the Vercel score.
- `vercelScore`: Vercel agent-readability score (0–100); null while running.

### `get_scan` (~60 tokens)

Get a previous scan by id

Fetches a completed or in-progress scan by its id. Only scans owned by the authenticated API key's user are returned.

Input parameters:

- `id` (string, required): The scan id returned by scan_site (also the share token in a /scan/<id> URL).

Output parameters:

- `accessibilityChecks`: Accessibility / layout-stability checks (A-series) run over the homepage.
- `accessibilityScore`: Accessibility / layout-stability sub-score (0–100) over the homepage WCAG checks; null when none ran. Separate from the Vercel score.
- `id` (string): The scan id.
- `llmstxtScore`: llms.txt score (0–100).
- `pagesDiscovered`: Number of pages discovered.
- `pagesScanned`: Number of pages scanned.
- `pollUrl`: Poll URL while the scan is still running.
- `protocolResults`: Agent-protocol checks (C-series) that ran — only for endpoints the site actually exposes.
- `rootUrl`: The scanned site URL.
- `shareUrl`: Path to the shareable report (/scan/<id>).
- `status` (string): Scan status: running, completed, or failed.
- `vercelRating`: Rating band for the Vercel score.
- `vercelScore`: Vercel agent-readability score (0–100); null while running.

### `ask` (~194 tokens)

Ask Agent Ready in natural language

Natural-language search (NLWeb /ask) over Agent Ready's own content — scoring methodology, the check registry, the specs it validates, and the content library (explainers, comparisons, how-to guides, glossary). Returns Schema.org-typed result objects. Optional itemType narrows to a corpus type; mode 'summarize' adds an extractive summary.

Input parameters:

- `itemType` (string): Restrict results to a content type: methodology, checks, specs, llms-txt, check, page (explainers/guides/glossary), or any (default: all types).
- `mode` (string): "list" (default) returns matching items; "summarize" returns a synthesized answer.
- `q` (string, required): Natural-language question to search Agent Ready's docs, scoring methodology, check registry, and content library (explainers, comparisons, how-to guides, glossary).

Output parameters:

- `message`: Extractive summary when mode is 'summarize'.
- `results` (array): Matching result items (Schema.org-typed).

## Diagnostics

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

## Score history

- 2026-08-03: 83
- 2026-08-02: 83
- 2026-08-01: 82
- 2026-07-31: 82
- 2026-07-30: 77
- 2026-07-29: 77
- 2026-07-28: 76
- 2026-07-27: 75
- 2026-07-26: 75

## Links

- Remote endpoint: https://agent-ready.dev/api/v1/mcp
- Repository: https://github.com/mlava/agent-ready-mcp
- Website: https://agent-ready.dev/
- Changelog RSS feed: https://verifymcp.io/servers/mlava-agent-ready-mcp/api-v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mlava-agent-ready-mcp/api-v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mlava-agent-ready-mcp/api-v1-mcp