check_document — Document Integrity Validator MCP Tool Read-only
check_document
(check document) is one of 2 tools on the
Document Integrity Validator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_document from your client
- Claude Code Document Integrity Validator check_document run in your project directory
- Claude Desktop Document Integrity Validator check_document ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Document Integrity Validator check_document ~/.cursor/mcp.json
- VS Code Document Integrity Validator check_document .vscode/mcp.json
- Zed Document Integrity Validator check_document ~/.config/zed/settings.json
- Windsurf Document Integrity Validator check_document ~/.codeium/windsurf/mcp_config.json
- Cline Document Integrity Validator check_document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Document Integrity Validator check_document ~/.gemini/settings.json
- Grok Document Integrity Validator check_document .mcp.json (in your project root)
- ChatGPT Document Integrity Validator check_document Settings → Connectors → Advanced → Developer mode
- Claude.ai Document Integrity Validator check_document Settings → Connectors → Add custom connector
- LangChain Document Integrity Validator check_document pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http document-integrity-validator-mcp https://document-integrity-validator-mcp-production.up.railway.app/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.