Home › Other › LLMVerify

LLMVerify

Local-first MCP server for LLM output verification — risk signals, injection and PII checks.

TypeScript
★ 19 stars Last pushed 2026-11-03 License: NOASSERTION

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Package (npm 1.8.0)

npx -y llmverify@1.8.0

Or add to your MCP client config:

{
  "mcpServers": {
    "llmverify-npm": {
      "command": "npx",
      "args": [
        "-y",
        "llmverify@1.8.0"
      ],
      "env": {
        "LLMVERIFY_AUDIT_HASH_KEY": "<YOUR_VALUE>"
      }
    }
  }
}
  • LLMVERIFY_MCP_MAX_INPUT_CHARS — Max characters accepted in a content/input argument
  • LLMVERIFY_MCP_TIMEOUT_MS — Per-tool wall-clock timeout in milliseconds
  • LLMVERIFY_MCP_MAX_OUTPUT_ITEMS — Cap on any single output array
  • LLMVERIFY_MCP_MAX_TEXT_FIELD_CHARS — Cap on any single text field in output
  • LLMVERIFY_HOME — Base directory for engine local state
  • LLMVERIFY_AUDIT_DIR — Audit JSONL directory
  • LLMVERIFY_LOG_DIR — Operational log directory
  • LLMVERIFY_BASELINE_DIR — Drift baseline directory
  • LLMVERIFY_USAGE_FILE — Usage counter file
  • LLMVERIFY_AUDIT_HASH_KEY secret — Enables keyed hmac-sha256 content hashes in audit records
  • LLMVERIFY_AUDIT_NO_CONTENT_HASH — Set to 1 to disable content hashes in audit records

This server takes extra arguments — see its repository.

Related servers

Data from the Official MCP Registry