check_agent_readiness — number7even website check MCP Tool Read-only
check_agent_readiness
(check agent readiness) is one of 3 tools on the
number7even website check
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 number7even website check check_agent_readiness run in your project directory
- Claude Desktop number7even website check check_agent_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor number7even website check check_agent_readiness ~/.cursor/mcp.json
- VS Code number7even website check check_agent_readiness .vscode/mcp.json
- Zed number7even website check check_agent_readiness ~/.config/zed/settings.json
- Windsurf number7even website check check_agent_readiness ~/.codeium/windsurf/mcp_config.json
- Cline number7even website check check_agent_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI number7even website check check_agent_readiness ~/.gemini/settings.json
- Grok number7even website check check_agent_readiness .mcp.json (in your project root)
- ChatGPT number7even website check check_agent_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai number7even website check check_agent_readiness Settings → Connectors → Add custom connector
- LangChain number7even website check check_agent_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http website-check https://number7even.com/api/mcp/Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 7 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.