Skip to content
mcp/harbor

Gemini CLI Document Integrity Validator check_document_package

How to: Gemini CLI Document Integrity Validator check_document_package

client:Gemini CLI transport:streamable-http tool:check_document_package

Add Document Integrity Validator to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "document-integrity-validator-mcp": {
      "httpUrl": "https://document-integrity-validator-mcp-production.up.railway.app/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something check_document_package does. Gemini CLI lists the server's tools on connect and calls check_document_package itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Document Integrity Validator's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI 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.

Document Integrity Validator MCP server