# AgentsReady (remote · agentsready.dev)

Audit any website for AI agents and AI search (AEO): llms.txt, AI bots, schema. Score plus fixes.

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

## Components

- remote · `agentsready.dev`: 78/100 (this document), [markdown](https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready.md), [page](https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready)

## Channel facts

- Endpoint: `https://agentsready.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-11-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 563 tokens (~112/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the AgentsReady MCP server?

AgentsReady is a hosted endpoint at https://agentsready.dev/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 dev-agentsready-agentsready 'https://agentsready.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-agentsready-agentsready": {
      "url": "https://agentsready.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-agentsready-agentsready": {
      "type": "http",
      "url": "https://agentsready.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-agentsready-agentsready]
url = "https://agentsready.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-agentsready-agentsready": {
      "type": "remote",
      "url": "https://agentsready.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-agentsready-agentsready --url 'https://agentsready.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-agentsready-agentsready:
    url: "https://agentsready.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-agentsready-agentsready": {
      "Transport": "http",
      "Url": "https://agentsready.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-agentsready-agentsready -t streamable-http -u 'https://agentsready.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-agentsready-agentsready": {
      "type": "http",
      "url": "https://agentsready.dev/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-11-22 (score 78, +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-11-20 (score 77, +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-11-18 (score 76, +1)

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

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

### 2026-11-15 (score 74, +2)

- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-06-18 → 2026-07-28
- [functional] Server version: 1.2.2 → 1.3.0

### 2026-11-14 (score 72, 0)

- [functional] Server version: 1.2.0 → 1.2.2

### 2026-11-13 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 71)

First indexed and scored.

## MCP tools (5)

### `check_site` (~204 tokens)

Check a site's agent readiness

Audit a website for AI agents and AI search (AEO/GEO): scan it the way ChatGPT, Claude and Perplexity fetch it and score it 0-100 (60 core points plus 40 for the job). Checks robots.txt rules for AI bots, bot walls and firewalls, server-rendered content, structured data, llms.txt, sitemap, pricing and sign-up pages, OpenAPI and MCP. Returns the score, every failed check with its fix, and the checks it passed. Read-only scan, cached for 24 hours; it does not run an agent on the site.

Input parameters:

- `domain` (string, required): The site to check, like example.com
- `job` (string): What agents should do on the site: recommend (answer questions about it), buy, signup, api (get an API key) or personal (a person's own site: who they are, their work, how to reach them). Leave out t…

### `get_fixes` (~141 tokens)

Get the fix prompt for a site

Return a ready-to-run task list for a coding agent that fixes every failed agent-readiness and AI-search check on the site (for example adding llms.txt, unblocking AI crawlers, adding structured data), biggest first, with how to verify each change. Same scan as check_site.

Input parameters:

- `domain` (string, required): The site to check, like example.com
- `job` (string): What agents should do on the site: recommend (answer questions about it), buy, signup, api (get an API key) or personal (a person's own site: who they are, their work, how to reach them). Leave out t…

### `get_checklist` (~74 tokens)

The agent readiness checklist

The full 50-item checklist for getting recommended by AI assistants and letting their agents sign up, grouped by area, with how to pass each item. Pass kind "personal" for the list for a person's own site (portfolio, blog, GitHub Pages).

Input parameters:

- `kind` (string): company (default) or personal

### `get_standard` (~45 tokens)

How the score works

Every check in the AgentsReady score with its points and fix: the 60 core points and the 40 points for each job (recommend, buy, signup, api, personal).

### `lookup_vendor` (~59 tokens)

Look up a software vendor's ranking

Where a software vendor ranks in the AgentsReady category rankings (CRM, help desk, payments and 17 more): score, rank, bot wall, MCP server and biggest gap.

Input parameters:

- `domain` (string, required): The site to check, like example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready#diagnostics

## Score history

- 2026-11-22: 78
- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71

## Common questions

### What is the AgentsReady MCP server?

AgentsReady is an MCP server listed in the public MCP registry as dev.agentsready/agentsready. Audit any website for AI agents and AI search (AEO): llms.txt, AI bots, schema. Score plus fixes. This page covers its hosted endpoint (https://agentsready.dev/mcp).

### Is the AgentsReady MCP server safe to use?

AgentsReady 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 AgentsReady MCP server expose?

AgentsReady exposes 5 tools: check_site, get_fixes, get_checklist, get_standard, lookup_vendor. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

### Does the AgentsReady MCP server require authentication?

No. We connected to AgentsReady without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AgentsReady MCP server still maintained?

AgentsReady is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the AgentsReady MCP server?

VerifyMCP ran 13 checks on AgentsReady, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agentsready.dev/mcp
- Website: https://agentsready.dev/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready.json
- HTML version of this page: https://verifymcp.io/servers/dev-agentsready-agentsready/agentsready
