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