--- title: "Agent Ready MCP server | Agent MCP Directory" description: "Agent Ready has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/agent-ready-dev site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Agent Ready MCP server | Agent MCP Directory > Agent Ready has an open MCP server with 3 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/agent-ready-dev Site: Agent MCP Directory Last reviewed: 2026-11-05 # Agent Ready: MCP server, CLI and agent surfaces Yes: Agent Ready runs a public MCP server at agent-ready.dev that listed 3 tools to a client with no credentials on 4 November 2026. Examples: scan\_site, get\_scan, ask. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for agent-ready.dev is 94, grade A, read on 5 November 2026. ## Fact sheet | Company | Agent Ready | | --- | --- | | Domain | agent-ready.dev | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 94, grade A; Ora scanned the domain on 10 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for agent-ready.dev, a vendor-published score) | | Company found through | the GitHub MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://agent-ready.dev/api/v1/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | agent-ready 1.0.0 | | Capabilities | resources, tools, prompts | | Tools | 3 | | Resources | 5 | | Prompts | 3 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 1,437 ms over 1 attempt | ### Tools listed 3 tools - scan\_site - get\_scan - ask ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:20Z https://agent-ready.dev/api/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1395 ms - 20:01:57Z https://agent-ready.dev/api/v1/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1437 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://agent-ready.dev/api/v1/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Agent Ready. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: agent-ready.dev (JSON, via a direct request). | | WebMCP in the initial HTML | Detected on the home page by the shared crawl. | | MCP discovery file | Found: agent-ready.dev/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | Found: agent-ready.dev/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Not found (the crawl got a non-200 answer). | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Found: agent-ready.dev/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/agent-ready-dev/index.md) ## Sources - [Ora score page for agent-ready.dev](https://ora.ai/score/agent-ready.dev?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 10 October 2026, read from GET /api/score) - [Where Agent Ready was found](https://github.com/mcp/mlava/agent-ready-mcp), read 4 November 2026 - [Agent Ready website](https://agent-ready.dev), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026