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