LLMVerify MCP Server

by subodhkcio.github.subodhkc/llmverifyv1.8.0

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

18Node.jsstdioofficial registry

context tax

pending

security

92/100

cold start

pending

freshness

Active9d ago

Our reading of LLMVerify, from the data

LLMVerify is a ai & llm tools MCP server from subodhkc, listed in the official MCP Registry.

We haven't measured its tool list yet, so its token cost is unknown.

Maintenance is active: the last public signal was 9 days ago (2026-10-09). For comparison, 59% of ai & llm tools servers are active or maintained.

With 18 GitHub stars it ranks #390 of 3,169 ai & llm tools servers we index.

It runs locally on your machine over stdio and needs one secret (LLMVERIFY_AUDIT_HASH_KEY); use a scoped, least-privilege key.

Install LLMVerify MCP server

claude mcp add llmverify -e LLMVERIFY_AUDIT_HASH_KEY='<llmverify-audit-hash-key>' -- npx -y llmverify mcp

{
  "mcpServers": {
    "llmverify": {
      "command": "npx",
      "args": [
        "-y",
        "llmverify",
        "mcp"
      ],
      "env": {
        "LLMVERIFY_AUDIT_HASH_KEY": "<llmverify-audit-hash-key>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "llmverify": {
      "command": "npx",
      "args": [
        "-y",
        "llmverify",
        "mcp"
      ],
      "env": {
        "LLMVERIFY_AUDIT_HASH_KEY": "<llmverify-audit-hash-key>"
      }
    }
  }
}

Settings → Developer → Edit Config (claude_desktop_config.json), then restart.

{
  "servers": {
    "llmverify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "llmverify",
        "mcp"
      ],
      "env": {
        "LLMVERIFY_AUDIT_HASH_KEY": "<llmverify-audit-hash-key>"
      }
    }
  }
}

Add to .vscode/mcp.json in your workspace.

{
  "mcpServers": {
    "llmverify": {
      "command": "npx",
      "args": [
        "-y",
        "llmverify",
        "mcp"
      ],
      "env": {
        "LLMVERIFY_AUDIT_HASH_KEY": "<llmverify-audit-hash-key>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

Configuration

Variable	Required	Secret	Description
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	—	yes	Enables keyed hmac-sha256 content hashes in audit records
LLMVERIFY_AUDIT_NO_CONTENT_HASH	—	—	Set to 1 to disable content hashes in audit records

Security signals

92/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.

Deductions

No license detected-5
No security policy (SECURITY.md)-3

Checks

✓Repository hygiene (archived, activity, license, security policy)
○Package metadata (install scripts, provenance) — pending
○Tool descriptions (prompt-injection and hidden-text heuristics) — pending
○Source scan (secrets, CVEs, risky code) by vectra-guard — pending

Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules

Freshness

Active — last maintenance signal 9d ago. The newest of the signals below sets the band.

Last commit (default branch)
2026-10-09 · 9d ago · GitHub
Latest release
no data · GitHub
Package published
no data · npm/PyPI
Registry entry updated
2026-10-09 · 9d ago · official registry · v1.8.0

How it compares in AI & LLM Tools

Against the most-starred ai & llm tools servers we index. Token cost is per model turn, measured from each server's live tool list.

Server	Stars	Tools	Tokens / turn	Freshness	Runs
LLMVerify (this)	18	—	not measured	Active	local
Memory	91,356	—	not measured	Active	local
Claude Flow	76,638	—	not measured	Active	local
Next AI Draw.io	36,318	—	not measured	Active	local
Serena Agent	30,371	—	not measured	Active	local
Trycua	30,160	—	not measured	Active	—

All ai & llm tools MCP servers

FAQ

›How do I install the LLMVerify MCP server in Claude Code?

Run: claude mcp add llmverify -e LLMVERIFY_AUDIT_HASH_KEY='<llmverify-audit-hash-key>' -- npx -y llmverify mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does LLMVerify require an API key?

Yes. It expects LLMVERIFY_AUDIT_HASH_KEY, of which 1 is a secret.

›Can I use LLMVerify as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is LLMVerify in the official MCP registry?

Yes, as io.github.subodhkc/llmverify.

Sources and method

Official MCP Registry entry: updated 2026-10-09
GitHub repository: fetched 2026-10-19
Package registry (npm / PyPI): listed
Security signals, computed by us: 2026-10-19
Last checked against all sources: 2026-10-19

The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.