Ejentum MCP
@ejentum
Exposes the four Ejentum cognitive harnesses (reasoning, code, anti-deception, memory) as MCP tools any agentic client can call. Drop-in scaffolding that catches LLM failure modes like sycophancy, hallucination, and reasoning shortcuts.
概要
What is Ejentum MCP?
Ejentum MCP provides four cognitive harness tools (harness_reasoning, harness_code, harness_anti_deception, harness_memory) that return structured reasoning scaffolds to catch common LLM failure modes (sycophancy, hallucination, causal shortcuts, premature conclusions). It is a thin, stateless wrapper around the Ejentum Logic API and works in any MCP-compatible client (Claude Desktop, Cursor, Windsurf, Claude Code, n8n).
How to use Ejentum MCP?
Install via Smithery (one‑click) or manually by adding a JSON block to your MCP client’s config, setting the EJENTUM_API_KEY environment variable. Each harness tool accepts a single query argument (a 1–2 sentence framing). The calling LLM absorbs the returned scaffold internally and shapes its user‑facing answer with it; the user never sees the scaffold.
Key features of Ejentum MCP
- Four cognitive harness tools for different reasoning modes
- One‑click install via Smithery on all major MCP clients
- Stateless and lightweight — thin wrapper over the Ejentum Logic API
- Free tier with 100 calls (no credit card required)
- Cross‑platform (Node 18+) and cross‑client
Use cases of Ejentum MCP
- Multi‑step analysis, planning, diagnostics, and cross‑domain synthesis
- Code generation, refactoring, review, and debugging
- Detecting and rejecting sycophancy, hallucination, and manipulation pressure
- Perception sharpening, drift detection, and cross‑turn pattern recognition
FAQ from Ejentum MCP
What runtime does Ejentum MCP require?
Node.js 18+ is needed only for manual install. Smithery handles the runtime for you.
Where does my API key and data live?
Your API key is stored only in your local MCP client config and sent as a Bearer token to the Ejentum API. The MCP wrapper itself is stateless with no local logging, telemetry, or third‑party calls. The upstream Ejentum API counts requests for tier billing; query content is processed for the response and not retained beyond it.
How do I invoke the harness tools?
Explicitly (e.g., “use the harness_anti_deception tool to evaluate…”) or with soft suggestions (“reason about this”, “check this for sycophancy”). Autonomous calling is less reliable when the agent could answer well from native reasoning — this is a property of optional MCP tools in general.
What are the usage limits and pricing tiers?
Free tier: 100 calls lifetime (no card required). Ki (€19/mo): 5,000 calls/month. Haki (€49/mo): 10,000 calls/month plus -multi modes (not exposed in v0.1).
What errors can I encounter?
401 (unauthorized) – wrong or expired API key. 403 (forbidden) – the mode is not included in your tier. 429 (rate limit exceeded) – monthly cap reached. “Tool does not appear” – the client didn’t pick up the config change; restart the client. “EJENTUM_API_KEY is not set” – the client didn’t pass the env block to the MCP process.
