MCP.Market

emem, the verifiable memory protocol for the physical world MCP server

online · 100% uptime
by Vortx-AI·io.github.Vortx-AI/emem·v2.4.4·71 stars

Shared, verifiable memory for machines and AI. Encode where data lives; decode with any AI.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

not scanned yet

Adoption
Growing

71 stars

Reviews

Write one

Nobody has reviewed emem, the verifiable memory protocol for the physical world yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

emem, the verifiable memory protocol for the physical world tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How emem, the verifiable memory protocol for the physical world compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
547 ms
faster than 30% of 30,027 servers
GitHub stars
71
more than 95% of 28,706 servers

Release history: 4 versions in the registry since 2026-09-09, latest 2026-10-18, typically one every 11 days.

Install emem, the verifiable memory protocol for the physical world in Claude Code, Cursor or VS Code

claude mcp add --transport http emem https://emem.dev/mcp
Add to Cursor

What the publisher says

From the emem, the verifiable memory protocol for the physical world repository's README, as published. We do not edit it. Read it on GitHub

emem

emem is the external, shared world memory for AI agents. Gives your agents a world in common.

Two agents that share no model and no vendor can cite the same world fact and each check it alone. Satellites, CCTVs and agents' experiences fill the memory today; any machine that shows how it ran can join.

Try it, no key · Verify a fact · Use it in two minutes · Agent guide · Watch nine agents share one memory

A model answers from a distribution. emem answers from an address. Ask a model twice and you get two answers; ask emem a million times and the same signed bytes come back. The token is an address not a payload, it is the only thing that crosses between agents, hence no referential drift, compaction failures or handoff issues.

emem turns agent's observations, satellite records and camera evidence into a shared state substrate that any agent can use, reuse, share, cite and verify. Build research teams, coordinate across models and carry evidence into the next investigation. Long running agents need an external memory, adding in world facts minimises chances of drifts, corruptions and hallucinations.

Start here

One agent's evidence. Every agent's starting point.

A research agent spots a change. Another investigates the cause. A third builds on the findings.

emem gives them a common record outside any one model: the place, the observation, its source and a reference they can pass between systems. Each agent can return to that evidence and check what was signed.

Research together. Accumulate findings around evidence later agents can inspect.

Coordinate across models. Carry the same observation through a handoff.

Keep investigations moving. Recover signed notes and references when a session ends.

From orbit to shared state.

Space supplies the observations. emem makes them shared memory for intelligence on Earth.

Satellites observe landscapes and change over time. Available cameras add a view from the ground. emem keeps observations addressable, with their sources and dates, so different agents can work from the same recorded evidence.

Models bring the reasoning. emem supplies the common record.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

emem, the verifiable memory protocol for the physical world: common questions

Is emem, the verifiable memory protocol for the physical world MCP server safe?
Mostly: it is graded B (83/100). Read the emem, the verifiable memory protocol for the physical world safety report
How do I install emem, the verifiable memory protocol for the physical world?
It runs remotely at emem.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does emem, the verifiable memory protocol for the physical world need an API key?
No secret keys are declared. It reads 5 settings from the environment.
Is emem, the verifiable memory protocol for the physical world maintained?
The last commit was 22 days ago (2026-10-14). The latest release is v2.4.4.
Is emem, the verifiable memory protocol for the physical world up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does emem, the verifiable memory protocol for the physical world compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 547 ms (faster than 30% of 30,027 servers). Full comparison.