LLMVerify for Cursor
io.github.subodhkc/llmverify
Local-first MCP server for LLM output verification — risk signals, injection and PII checks.
client:Cursor
transport:stdio
runtime:npm
Install LLMVerify in Cursor
~/.cursor/mcp.json · windows: %USERPROFILE%\.cursor\mcp.json
{
"mcpServers": {
"llmverify": {
"type": "stdio",
"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>"
}
}
}
}
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs