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