LLMVerify MCP Server

What this does

LLMVerify exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

LLMVERIFY_MCP_MAX_INPUT_CHARS
LLMVERIFY_MCP_TIMEOUT_MS
LLMVERIFY_MCP_MAX_OUTPUT_ITEMS
LLMVERIFY_MCP_MAX_TEXT_FIELD_CHARS
LLMVERIFY_HOME
LLMVERIFY_AUDIT_DIR
LLMVERIFY_LOG_DIR
LLMVERIFY_BASELINE_DIR
LLMVERIFY_USAGE_FILE
LLMVERIFY_AUDIT_HASH_KEY
LLMVERIFY_AUDIT_NO_CONTENT_HASH

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install LLMVerify?

Run the Claude Code command in the install section to add LLMVerify to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with LLMVerify?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to LLMVerify as well.

Does LLMVerify need an API key?

Yes. Before it can run, set these environment variables: LLMVERIFY_MCP_MAX_INPUT_CHARS, LLMVERIFY_MCP_TIMEOUT_MS, LLMVERIFY_MCP_MAX_OUTPUT_ITEMS, LLMVERIFY_MCP_MAX_TEXT_FIELD_CHARS, LLMVERIFY_HOME, LLMVERIFY_AUDIT_DIR, LLMVERIFY_LOG_DIR, LLMVERIFY_BASELINE_DIR, LLMVERIFY_USAGE_FILE, LLMVERIFY_AUDIT_HASH_KEY, LLMVERIFY_AUDIT_NO_CONTENT_HASH. They go in the env block of your MCP config.