Cline Document Integrity Validator check_document_package
How to: Cline Document Integrity Validator check_document_package
Add Document Integrity Validator to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"document-integrity-validator-mcp": {
"url": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something check_document_package does. Cline lists the server's tools on connect and calls check_document_package itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Document Integrity Validator's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
Document Integrity Validator will not start until these are set, so check_document_package never becomes available.
-
ANTHROPIC_API_KEY
Same tool, other clients
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.