check_agent_readiness — Agent Ready Website Audit MCP Tool Read-only
check_agent_readiness
(check agent readiness) is one of 13 tools on the
Agent Ready Website Audit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_agent_readiness from your client
- Claude Code Agent Ready Website Audit check_agent_readiness run in your project directory
- Claude Desktop Agent Ready Website Audit check_agent_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Ready Website Audit check_agent_readiness ~/.cursor/mcp.json
- VS Code Agent Ready Website Audit check_agent_readiness .vscode/mcp.json
- Zed Agent Ready Website Audit check_agent_readiness ~/.config/zed/settings.json
- Windsurf Agent Ready Website Audit check_agent_readiness ~/.codeium/windsurf/mcp_config.json
- Cline Agent Ready Website Audit check_agent_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Ready Website Audit check_agent_readiness ~/.gemini/settings.json
- Grok Agent Ready Website Audit check_agent_readiness .mcp.json (in your project root)
- ChatGPT Agent Ready Website Audit check_agent_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Ready Website Audit check_agent_readiness Settings → Connectors → Add custom connector
- LangChain Agent Ready Website Audit check_agent_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-ready-mcp https://mcp.workpods.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.