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