emem, the verifiable memory protocol for the physical world
Shared, verifiable memory for machines and AI. Encode where data lives; decode with any AI
Reviews
No review yet. Used emem, the verifiable memory protocol for the physical world? Be the first to help others choose.What it does
emem, the verifiable memory protocol for the physical world is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3d ago (live check)Hosted endpoint
https://emem.dev/mcpstreamable-http
In Claude Code: claude mcp add --transport http emem-the-verifiable-memory-protocol-for-the-physical-world https://emem.dev/mcp
Install package
- DOCKER
ghcr.io/vortx-ai/emem:latest· runs as a server (streamable-http)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"emem-the-verifiable-memory-protocol-for-the-physical-world": {
"url": "https://emem.dev/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 3d agoONLINE emem, the verifiable memory protocol for the physical world answered an MCP connection on 14 Nov 2026 and introduced itself as emem 2.4.5 (MCP protocol 2025-06-18).
18 tools offered to AI assistants
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 way. The result is an `entity_token` (`emem:entity:<entity_cid>`) and a signed receipt that shows howemem_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 ground. The answer also lists, by topic, the bands and algorithms that you can recall there. For an Oemem_recall· Read the signed facts at a canonical address (cell64). When a band has no fact yet but has a registered materializer, the responder fetches it. A fact_cid names one signed attestation, so you can cite a fact and verify it again. Resolve theemem_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 for byte. Give this one string to another agent instead of a new description of the fact. The tool cheemem_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 TOP level of the answer, beside the full signed `fact` body. You do not split the token or call `GETemem_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` names. It checks the ed25519 signature with the embedded key. It returns `{valid, reason, failure_detaemem_memory_contradictions· Find where the corpus DISAGREES with itself (algebra: competing evidence). Two or more independent sources can sign different values for the same place, band and time. This tool returns that disagreement with a severity from 0 to 1 and a ciemem_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, resolves each one, and returns allow or deny with a reason that a machine can read: `EMEM-GUARD DENY <emem_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, verify, check for drift). Then it groups every other tool by the question it answers, each with a one-lineemem_ask· Answer a free-text question about a real-world location in one call. Signed satellite, elevation, water and built-up receipts support the answer. The tool sends the place and the question through the locate, recall and algorithm chain on thsearch· 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, place and signed value, and a stable `url` that serves those bytes. The query can be a place or a qfetch· 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, band, signing time and key. The id can be an `emem:fact:` citation, a bare fact_cid, or an `emem:ce
Show 6 more
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 match, it also returns the `drift` between your value and the value in emem. This step catches a transcriemem_memory_bundle· Combine N (cell, band, tslot?) triples into ONE signed envelope. Each triple goes through the standard recall path, which materializes on a miss. The tool puts the resulting fact_cids in a content-addressed envelope, and the responder signsemem_entity_resolve· Find the objects that agents connected to a phrase. The tool ranks them by INDEPENDENT corroboration, never by arrival order. Each candidate has `asserted_by`, `disputed_by`, `independent_attesters` and `corroboration` (`single_key` | `multemem_entity_link· Record a signed, ATTRIBUTED claim that a label or an external id (GERS, OSM, Wikidata) names an existing object. With `stance: "disputes"`, record that it does not. This is a write to the shared space: it changes what other agents resolve.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`, `score`, `lat`/`lng` and `band_used`, and a signed receipt over the vectors it read. `mode` sets temem_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 that the tool reads. Send only the fields in its row. The plan runs in the same call: you get results,
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 2.4.5 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Install package | ghcr.io/vortx-ai/emem:latest | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://emem.dev/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Package registries | oci | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://emem.dev | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/Vortx-AI/emem | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION07 Nov 20262.4.4 → 2.4.5
- VERSION18 Oct 20262.4.3 → 2.4.4
- VERSION10 Oct 20262.4.2 → 2.4.3
- VERSION29 Sept 20262.4.0 → 2.4.2
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is emem, the verifiable memory protocol for the physical world still online?
Free alerts · no account▲ 0Do you run emem, the verifiable memory protocol for the physical world? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about emem, the verifiable memory protocol for the physical world
How do I connect emem, the verifiable memory protocol for the physical world?
Use the hosted endpoint https://emem.dev/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does emem, the verifiable memory protocol for the physical world offer?
When Electra Index connected on 14 Nov 2026, it listed 18 tools: emem_entity, emem_locate, emem_recall, emem_memory_token, emem_memory_token_resolve, emem_verify_receipt, emem_memory_contradictions, emem_guard_verdict and more. The full list is in "Live check" above.
Is emem, the verifiable memory protocol for the physical world online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 3d ago.