lookup_manifest — ProofSnap Verify MCP Tool Read-only
lookup_manifest
(lookup manifest) is one of 1 tool on the
ProofSnap Verify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call lookup_manifest from your client
- Claude Code ProofSnap Verify lookup_manifest run in your project directory
- Claude Desktop ProofSnap Verify lookup_manifest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ProofSnap Verify lookup_manifest ~/.cursor/mcp.json
- VS Code ProofSnap Verify lookup_manifest .vscode/mcp.json
- Zed ProofSnap Verify lookup_manifest ~/.config/zed/settings.json
- Windsurf ProofSnap Verify lookup_manifest ~/.codeium/windsurf/mcp_config.json
- Cline ProofSnap Verify lookup_manifest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ProofSnap Verify lookup_manifest ~/.gemini/settings.json
- Grok ProofSnap Verify lookup_manifest .mcp.json (in your project root)
- ChatGPT ProofSnap Verify lookup_manifest Settings → Connectors → Advanced → Developer mode
- Claude.ai ProofSnap Verify lookup_manifest Settings → Connectors → Add custom connector
- LangChain ProofSnap Verify lookup_manifest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http proofsnap-verify https://mcp.getproofsnap.com/verify/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.