check_agent_tool_readiness — Boundary Guard x402 MCP Tool Read-only
check_agent_tool_readiness
(check agent tool readiness) is one of 6 tools on the
Boundary Guard x402
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_agent_tool_readiness from your client
- Claude Code Boundary Guard x402 check_agent_tool_readiness run in your project directory
- Claude Desktop Boundary Guard x402 check_agent_tool_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Boundary Guard x402 check_agent_tool_readiness ~/.cursor/mcp.json
- VS Code Boundary Guard x402 check_agent_tool_readiness .vscode/mcp.json
- Zed Boundary Guard x402 check_agent_tool_readiness ~/.config/zed/settings.json
- Windsurf Boundary Guard x402 check_agent_tool_readiness ~/.codeium/windsurf/mcp_config.json
- Cline Boundary Guard x402 check_agent_tool_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Boundary Guard x402 check_agent_tool_readiness ~/.gemini/settings.json
- Grok Boundary Guard x402 check_agent_tool_readiness .mcp.json (in your project root)
- ChatGPT Boundary Guard x402 check_agent_tool_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai Boundary Guard x402 check_agent_tool_readiness Settings → Connectors → Add custom connector
- LangChain Boundary Guard x402 check_agent_tool_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http boundary-guard-x402 https://x402-resource-scanner.vercel.app/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.