Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Agent Ready.
https://agent-ready.dev/api/v1/mcpnpx -y agent-ready-mcp{
"AGENT_READY_API_KEY": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-mlava-agent-ready-mcp": {
"command": "npx",
"args": [
"-y",
"agent-ready-mcp"
],
"env": {
"AGENT_READY_API_KEY": "YOUR_SECRET_VALUE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Agent Ready is an MCP server for Scan any URL for AI agent readability — Vercel Spec, llmstxt.org, and agent-protocol manifests.. It supports STDIO, HTTP transport.
Use the generated config in Install. This server runs with npx -y agent-ready-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://agent-ready.dev/api/v1/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://agent-ready.dev/api/v1/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://agent-ready.dev/api/v1/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://agent-ready.dev/api/v1/mcp.
Agent Ready uses STDIO, HTTP transport. Endpoint: https://agent-ready.dev/api/v1/mcp.
Agent Ready inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Agent Ready does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
agent-ready-mcpstdio | npm | 0.7.2 | Env: AGENT_READY_API_KEY secret |