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