ejentum-mcp
Registry code: 32ecd70a6b302a6a
Ejentum Cognitive Architecture Engine: Provides deterministic reasoning scaffolds, epistemic invariants, and anti-hallucination graph traversal for autonomous agents.
- endpoint
- https://api.ejentum.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is ejentum-mcp live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 67% of checks over the last 30 days.
- Is ejentum-mcp free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does ejentum-mcp have?
- 4 tools: ejentum_domains, ejentum_scaffold, ejentum_graph, ejentum_fts_search.
- Is ejentum-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 66.7%· all time 66.7%
last good check
of 4 tools
- degraded → live
- unknown → degraded· HTTP 502
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
ejentum_fts_search auth-required 13h ago
Execute sub-millisecond SQLite FTS5 full-text keyword search and BM25 ranking across the 311 deterministic reasoning abilities.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 4, "description": "Maximum number of abilities to return (1-10)." }, "query": { "type": "string", "description": "Keyword query or search terms (e.g. 'deadlock circular dependency sequence', 'database migration')." } } }arguments 17 linesejentum_domains unknown never probed
List the 6 invariant cognitive failure dimensions and primary failure modes mapped by Ejentum.
{ "type": "object", "properties": {} }arguments 4 linesejentum_scaffold unknown never probed
Retrieve a deterministic reasoning scaffold (Reasoning-Augmented Retrieval) to prevent hallucinations, causal inversion, and compounding multi-step failures.
{ "type": "object", "required": [ "query" ], "properties": { "mode": { "enum": [ "single", "stack", "graph" ], "type": "string", "default": "single", "description": "Reasoning mode: 'single' (Top-1 focused invariant), 'stack' (multi-tier synthesis), or 'graph' (synergy DAG traversal)." }, "query": { "type": "string", "description": "The user task, error trace, or diagnostic question to analyze." }, "stack_size": { "type": "integer", "default": 2, "description": "Number of complementary cognitive dimensions to stack (1-4)." } } }arguments 27 linesejentum_graph unknown never probed
Traverse the 933-edge cognitive synergy graph to compose a multi-hop Cognitive Directed Acyclic Graph (DAG) with Root, Prerequisite, Amplifier, and Fallback operators.
{ "type": "object", "properties": { "depth": { "enum": [ 1, 2 ], "type": "integer", "default": 1, "description": "Graph traversal depth: 1 (direct 1-hop dependencies) or 2 (recursive multi-hop chaining for autonomous agent workflows)." }, "query": { "type": "string", "description": "The complex task, system failure, or architecture question to analyze." }, "ability_id": { "type": "string", "description": "Optional specific root ability ID (e.g. 'CA-001', 'SI-039') to traverse directly." } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id32ecd70a6b302a6a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/32ecd70a6b302a6a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/32ecd70a6b302a6a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- api.ejentum.com self-inspect