get_verification_challenge — agentready MCP Tool Read-only
get_verification_challenge
(get verification challenge) is one of 11 tools on the
agentready
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_verification_challenge from your client
- Claude Code agentready get_verification_challenge run in your project directory
- Claude Desktop agentready get_verification_challenge ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentready get_verification_challenge ~/.cursor/mcp.json
- VS Code agentready get_verification_challenge .vscode/mcp.json
- Zed agentready get_verification_challenge ~/.config/zed/settings.json
- Windsurf agentready get_verification_challenge ~/.codeium/windsurf/mcp_config.json
- Cline agentready get_verification_challenge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentready get_verification_challenge ~/.gemini/settings.json
- Grok agentready get_verification_challenge .mcp.json (in your project root)
- ChatGPT agentready get_verification_challenge Settings → Connectors → Advanced → Developer mode
- Claude.ai agentready get_verification_challenge Settings → Connectors → Add custom connector
- LangChain agentready get_verification_challenge pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentready https://agentready-rho.vercel.app/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.