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