Arkheia MCP Server

Arkheia screens model responses for fabrication using behavioural fingerprinting. Works with Claude, GPT, Gemini, Grok, Llama, Mistral, and 30+ other

Local serverstdioPython

What is the Arkheia MCP MCP server?

Arkheia screens model responses for fabrication using behavioural fingerprinting. Works with Claude, GPT, Gemini, Grok, Llama, Mistral, and 30+ other models. One tool call. Real-time risk scoring. The arkheia mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

Adding it to your client

The server ships on npm as @arkheia/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • arkheia_verify — Score a model response for fabrication risk
  • arkheia_audit_log — Review your detection history
  • run_grok — Call Grok + screen for fabrication
  • run_gemini — Call Gemini + screen for fabrication
  • run_ollama — Call local Ollama model + screen
  • run_together — Call Together AI (Kimi, DeepSeek) + screen

Configuration

You will need 2 environment variables: PYTHONPATH, ARKHEIA_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Python 3.10+ - Node.js 18+ (for npx install) - Git

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the arkheia mcp mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Arkheia MCP's toolset — arkheia_verify, arkheia_audit_log, run_grok and 3 more — is a fair guide to whether it matches your workflow. It is maintained by arkheiaai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Arkheia MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
arkheia_verifyScore a model response for fabrication risk
arkheia_audit_logReview your detection history
run_grokCall Grok + screen for fabrication
run_geminiCall Gemini + screen for fabrication
run_ollamaCall local Ollama model + screen
run_togetherCall Together AI (Kimi, DeepSeek) + screen

How to install the Arkheia MCP MCP server

{
  "mcpServers": {
    "arkheia": {
      "command": "npx",
      "args": ["-y", "@arkheia/mcp-server"],
      "env": {
        "PYTHONPATH": "your-value",
        "ARKHEIA_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Python 3.10+ - Node.js 18+ (for npx install) - Git
VariableDescriptionRequired
PYTHONPATHFilesystem location the server is allowed to use.Optional
ARKHEIA_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Arkheia MCP to arkheia verify.
  • Use Arkheia MCP to arkheia audit log.
  • Use Arkheia MCP to run grok.

Frequently asked questions

It connects Arkheia MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (arkheia_verify, arkheia_audit_log, run_grok, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Arkheia MCP directly.