emem.dev
https://emem.dev/mcp
active Production-safe Score 90/100 http no auth
At a glance
| Endpoint | https://emem.dev/mcp |
|---|---|
| Source | https://github.com/Vortx-AI/emem/blob/main/examples/claude-code.mcp.json |
| Transport | http |
| Tools | 18 |
| Auth | none |
| First seen | 2026-07-07 11:50:12 |
| Last checked | 2026-11-17 21:47:00 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 759 / 1068 ms |
| Last successful check | 2026-11-17 21:47:00 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (18)
emem_entity— Give a real-world object (a bridge, a farm plot, a river, a named place) one shared identity. Every agent resolves this identity the same waemem_locate— Get the canonical address (cell64) of a real-world place. Every agent resolves a place to the same cell64, so two models refer to the same gemem_recall— Read the signed facts at a canonical address (cell64). When a band has no fact yet but has a registered materializer, the responder fetchesemem_memory_token— Make a citation handle, `emem:fact:<cell64>:<fact_cid>` (or `:<state_cid>`). Any agent or LLM resolves it to the same signed object, byte foemem_memory_token_resolve— Read a `emem:fact:<cell64>:<fact_cid>` citation handle and return the reading that it cites. `value`, `unit`, `band` and `kind` are at the Temem_verify_receipt— Verify a signed receipt on the server. The tool builds the canonical preimage again, under the rule that the receipt's `preimage_version` naemem_memory_contradictions— Find where the corpus DISAGREES with itself (algebra: competing evidence). Two or more independent sources can sign different values for theemem_guard_verdict— Run the emem-guard policy checks on text before you send it. The checks use this responder's corpus. The tool finds every emem: citation, reemem_tools— The map of emem's tools, and the one tool that finds all the others. It gives the working loop in order (name, ground, cite, resolve, verifyemem_ask— Answer a free-text question about a real-world location in one call. Signed satellite, elevation, water and built-up receipts support the ansearch— Search emem's signed corpus and get results as citations. Each entry is one signed fact. It has an `id` to dereference, a `title` with band,fetch— Dereference an id from `search`. You get the reading in one line, then the signed body, the URL that serves those bytes, and metadata: cell,emem_echo_verify— Grade a value that you will emit against the signed fact that your citation cites. The tool returns `matches`. When the value does not matchemem_memory_bundle— Combine N (cell, band, tslot?) triples into ONE signed envelope. Each triple goes through the standard recall path, which materializes on aemem_entity_resolve— Find the objects that agents connected to a phrase. The tool ranks them by INDEPENDENT corroboration, never by arrival order. Each candidateemem_entity_link— Record a signed, ATTRIBUTED claim that a label or an external id (GERS, OSM, Wikidata) names an existing object. With `stance: "disputes"`,emem_find_similar— Find the k nearest cells in the corpus by cell embedding or by an inline vector. The answer has `neighbors`, nearest first, each with `cell`emem_intent— State what you want in one typed object and get the answer. You do not choose a primitive. `type` selects the intent AND the other fields th
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:47:00 | ✓ | ✓ | 925 ms | 90 | active |
| 2026-11-17 21:31:55 | ✓ | ✓ | 636 ms | 90 | active |
| 2026-11-17 21:16:46 | ✓ | ✓ | 713 ms | 90 | active |
| 2026-11-17 21:01:44 | ✓ | ✓ | 704 ms | 90 | active |
| 2026-11-17 20:46:22 | ✓ | ✓ | 614 ms | 90 | active |
| 2026-11-17 20:31:21 | ✓ | ✓ | 606 ms | 90 | active |
| 2026-11-17 20:16:14 | ✓ | ✓ | 776 ms | 90 | active |
| 2026-11-17 20:00:24 | ✓ | ✓ | 899 ms | 90 | active |
| 2026-11-17 19:45:21 | ✓ | ✓ | 611 ms | 90 | active |
| 2026-11-17 19:30:03 | ✓ | ✓ | 1118 ms | 87 | active |
| 2026-11-17 19:15:01 | ✓ | ✓ | 611 ms | 90 | active |
| 2026-11-17 18:59:15 | ✓ | ✓ | 638 ms | 90 | active |
| 2026-11-17 18:44:14 | ✓ | ✓ | 695 ms | 90 | active |
| 2026-11-17 18:29:13 | ✓ | ✓ | 634 ms | 90 | active |
| 2026-11-17 18:14:11 | ✓ | ✓ | 726 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://emem.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/emem-dev-mcp # JSON