LLMVerify MCP Server

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

Packages and local setup

The published npm package is llmverify, version 1.8.0. Its declared MCP transport is stdio.

The package declares 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: 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 package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.8.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.