# Agent Ready Report (remote · scan.agenticplug.ai)

Scan any public website and see how ready it is for AI agents and AI search, explained plainly.

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

## Components

- remote · `scan.agenticplug.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-agenticplug-agent-ready-report/scan.md), [page](https://verifymcp.io/servers/ai-agenticplug-agent-ready-report/scan)

## Channel facts

- Endpoint: `https://scan.agenticplug.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 608 tokens (~304/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Agent Ready Report MCP server?

Agent Ready Report is a hosted endpoint at https://scan.agenticplug.ai/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 ai-agenticplug-agent-ready-report 'https://scan.agenticplug.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-agenticplug-agent-ready-report": {
      "url": "https://scan.agenticplug.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-agenticplug-agent-ready-report": {
      "type": "http",
      "url": "https://scan.agenticplug.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-agenticplug-agent-ready-report]
url = "https://scan.agenticplug.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-agenticplug-agent-ready-report": {
      "type": "remote",
      "url": "https://scan.agenticplug.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-agenticplug-agent-ready-report --url 'https://scan.agenticplug.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-agenticplug-agent-ready-report:
    url: "https://scan.agenticplug.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-agenticplug-agent-ready-report": {
      "Transport": "http",
      "Url": "https://scan.agenticplug.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-agenticplug-agent-ready-report -t streamable-http -u 'https://scan.agenticplug.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-agenticplug-agent-ready-report": {
      "type": "http",
      "url": "https://scan.agenticplug.ai/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-04 (score 78, +1)

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

### 2026-11-02 (score 77, +1)

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

### 2026-10-31 (score 76, +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-10-29 (score 75, +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-10-27 (score 74, +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-10-24 (score 73, +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-10-22 (score 72, +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-10-20 (score 71, +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.

## MCP tools (2)

### `scan_website` (~311 tokens)

Scan a website for agent readiness

Scan a public website and report how ready it is for AI agents and AI search: which checks pass, which are missing, and what each check is, in plain English and technically. Covers 35 checks in three groups: agent readiness (robots.txt and AI crawler rules, sitemap, Link headers, DNS-AID, markdown for agents, Content Signals, API catalog, OAuth discovery, auth.md, MCP server card, A2A agent card, agent skills, WebMCP, ARD), agentic commerce (x402, MPP, UCP, ACP, AP2; scored only for sites that sell online), and AI search foundations (HTTPS, AI crawler access, indexability, content without JavaScript, heading structure, title and description, canonical URL, structured data, business identity markup, language, response time). Use when someone asks whether their website is ready for AI agents, AI search, ChatGPT, Claude, Perplexity, Muse or agentic commerce. A scan takes 5 to 30 seconds.

Input parameters:

- `detail` (string): "standard": findings with plain-English and technical explanations. "full": adds pass criteria, request-by-request evidence and source links.
- `sells_online` (string): Whether the site sells online. "auto" detects it from the homepage; use "yes" or "no" when the owner has said.
- `url` (string, required): The website to scan, e.g. "example.com" or "https://www.example.com".

### `explain_check` (~97 tokens)

Explain an agent-readiness check

Explain one agent-readiness check in depth: what it is, why it matters for AI agents and AI search, exactly how the scanner tests it, what counts as a pass, and the official sources. Call with no check_id to list every check.

Input parameters:

- `check_id` (string): The check's id, as shown in a scan report (e.g. "dnsAid", "aiCrawlerAccess"). Omit to list all checks.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-agenticplug-agent-ready-report/scan#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 67
- 2026-10-12: 67
- 2026-10-11: 66
- 2026-10-10: 66

## Common questions

### What is the Agent Ready Report MCP server?

Agent Ready Report is an MCP server listed in the public MCP registry as ai.agenticplug/agent-ready-report. Scan any public website and see how ready it is for AI agents and AI search, explained plainly. This page covers its hosted endpoint (https://scan.agenticplug.ai/mcp).

### Is the Agent Ready Report MCP server safe to use?

Agent Ready Report 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 Agent Ready Report MCP server expose?

Agent Ready Report exposes 2 tools: scan_website, explain_check. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.

### Does the Agent Ready Report MCP server require authentication?

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

### Is the Agent Ready Report MCP server still maintained?

Agent Ready Report is still listed as active in the MCP registry. We last reached this channel on 5 November 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://scan.agenticplug.ai/mcp
- Website: https://agenticplug.ai/agent-ready-report
- Changelog RSS feed: https://verifymcp.io/servers/ai-agenticplug-agent-ready-report/scan.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-agenticplug-agent-ready-report/scan.json
- HTML version of this page: https://verifymcp.io/servers/ai-agenticplug-agent-ready-report/scan