Skip to content
mcp/harbor
Zed

LLMVerify for Zed

io.github.subodhkc/llmverify

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

client:Zed transport:stdio runtime:npm

Install LLMVerify in Zed

~/.config/zed/settings.json · windows: %APPDATA%\Zed\settings.json

Held in this page only — never stored, logged, or sent anywhere but back to your screen. 

{
  "context_servers": {
    "llmverify": {
      "command": "npx",
      "args": [
        "-y",
        "llmverify"
      ],
      "env": {
        "LLMVERIFY_MCP_MAX_INPUT_CHARS": "<LLMVERIFY_MCP_MAX_INPUT_CHARS>",
        "LLMVERIFY_MCP_TIMEOUT_MS": "<LLMVERIFY_MCP_TIMEOUT_MS>",
        "LLMVERIFY_MCP_MAX_OUTPUT_ITEMS": "<LLMVERIFY_MCP_MAX_OUTPUT_ITEMS>",
        "LLMVERIFY_MCP_MAX_TEXT_FIELD_CHARS": "<LLMVERIFY_MCP_MAX_TEXT_FIELD_CHARS>",
        "LLMVERIFY_HOME": "<LLMVERIFY_HOME>",
        "LLMVERIFY_AUDIT_DIR": "<LLMVERIFY_AUDIT_DIR>",
        "LLMVERIFY_LOG_DIR": "<LLMVERIFY_LOG_DIR>",
        "LLMVERIFY_BASELINE_DIR": "<LLMVERIFY_BASELINE_DIR>",
        "LLMVERIFY_USAGE_FILE": "<LLMVERIFY_USAGE_FILE>",
        "LLMVERIFY_AUDIT_HASH_KEY": "<LLMVERIFY_AUDIT_HASH_KEY>",
        "LLMVERIFY_AUDIT_NO_CONTENT_HASH": "<LLMVERIFY_AUDIT_NO_CONTENT_HASH>"
      }
    }
  }
}

Merge this into your existing settings object — do not replace the file. Zed docs

LLMVerify in other clients

LLMVerify MCP server