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