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