Agent Ready
by agent-ready.dev in Search & web
Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.
https://agent-ready.dev/api/v1/mcp- Tools
- 3
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 881 ms
- 1.4 s slowest 5%
- Last check
- Passed
- 5 h ago, next in 2 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"agent-ready": {
"type": "http",
"url": "https://agent-ready.dev/api/v1/mcp"
}
}
}3 tools
- scan_site
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.
- get_scan
Fetches a completed or in-progress scan by its id. Only scans owned by the authenticated API key's user are returned.
- ask
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…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 5 h ago | Passed | 200 | 886 ms |
| 15 h ago | Passed | 200 | 268 ms |
| 25 h ago | Passed | 200 | 838 ms |
| 35 h ago | Passed | 200 | 938 ms |
| 45 h ago | Passed | 200 | 258 ms |
Show 9 older checks
| 2 days ago | Passed | 200 | 922 ms |
| 3 days ago | Passed | 200 | 881 ms |
| 3 days ago | Passed | 200 | 884 ms |
| 3 days ago | Passed | 200 | 869 ms |
| 4 days ago | Passed | 200 | 895 ms |
| 4 days ago | Passed | 200 | 400 ms |
| 5 days ago | Passed | 200 | 872 ms |
| 5 days ago | Passed | 200 | 1.4 s |
| 5 days ago | Passed | 200 | 1.1 s |