verify_purchase — Agent Purchase Verification MCP Tool
verify_purchase
(verify purchase) is one of 1 tool on the
Agent Purchase Verification
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_purchase from your client
- Claude Code Agent Purchase Verification verify_purchase run in your project directory
- Claude Desktop Agent Purchase Verification verify_purchase ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Purchase Verification verify_purchase ~/.cursor/mcp.json
- VS Code Agent Purchase Verification verify_purchase .vscode/mcp.json
- Zed Agent Purchase Verification verify_purchase ~/.config/zed/settings.json
- Windsurf Agent Purchase Verification verify_purchase ~/.codeium/windsurf/mcp_config.json
- Cline Agent Purchase Verification verify_purchase ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Purchase Verification verify_purchase ~/.gemini/settings.json
- Grok Agent Purchase Verification verify_purchase .mcp.json (in your project root)
- ChatGPT Agent Purchase Verification verify_purchase Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Purchase Verification verify_purchase Settings → Connectors → Add custom connector
- LangChain Agent Purchase Verification verify_purchase pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-purchase-verification https://web-production-855eb4.up.railway.app/mcp/
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.