emem
listing.by
Read signed, citable facts about physical places and share them between agents as verifiable tokens.
listing.connect
listing.explain.none
listing.note.none listing.note.none_direct
listing.share.h
listing.share.p
mcp.tc/i/ememlisting.about
emem is a shared memory for AI agents, filled with satellite, elevation, water, air quality and other geospatial readings. Each place gets one address (cell64) and each observation is a signed fact with a content hash, so two agents can cite the same fact and check the signature without trusting each other. Tools cover place lookup, fact recall, entity identities, citation tokens, receipt verification, contradiction scans and similarity search.
The hosted endpoint at emem.dev/mcp uses streamable HTTP and needs no sign-in or API key for reads. Writes to shared spaces are tiered and need a signature. The server also ships as a Docker image (ghcr.io/vortx-ai/emem) and exposes a short tool list plus emem_tools to discover the rest.
listing.can
- Resolve a place name or coordinates to a canonical cell64 address
- Recall signed facts for a place and band, with auto-materialization
- Mint and resolve emem:fact: citation tokens
- Verify receipts and check claimed values against signed facts
- Scan for disagreement between attesters on the same place and band
- Mint and resolve canonical entity identities for real-world objects
- Find similar places by embedding
- Ask free-text questions about a location
listing.tools 18
emem_entitylisting.hint.writesMint or get a canonical shared identity for a real-world object.
emem_locatelisting.hint.roResolve a place to a cell64 address and list the bands available there.
emem_recalllisting.hint.writesRead signed facts at a cell, materializing them on a miss.
emem_memory_tokenlisting.hint.roCompose an emem:fact: citation handle for a signed fact.
emem_memory_token_resolvelisting.hint.roDereference a memory token to its value, unit, band and signed fact.
emem_verify_receiptlisting.hint.roVerify a signed ed25519 receipt server-side.
emem_memory_contradictionslisting.hint.roFind places where independent attesters signed different values.
emem_guard_verdictlisting.hint.roCheck whether emem citations in a draft text resolve and verify.
emem_toolslisting.hint.roList the full tool surface, search it, or get one tool's schema.
emem_asklisting.hint.writesAnswer a free-text question about a location from signed receipts.
searchlisting.hint.writesSearch signed facts for a place and return them as citable results.
fetchlisting.hint.writesOpen a search result, fact citation or cell handle and read the signed record.
listing.tools_more
emem_echo_verifylisting.hint.roCompare a value you plan to publish with the signed fact it cites.
emem_memory_bundlelisting.hint.writesCompose several facts into one signed bundle envelope.
emem_entity_resolvelisting.hint.roResolve a phrase or entity token to ranked canonical objects.
emem_entity_linklisting.hint.writesRecord a signed claim that a label or external ID denotes an object.
emem_find_similarlisting.hint.writesFind nearest-neighbour cells by embedding using cosine or hamming scoring.
emem_intentlisting.hint.writesDescribe an intent as a typed object and get the executed result.
listing.prov.live_on listing.prov.hints
listing.prompts
Has the area around 45.434, 12.323 flooded historically? Cite the signed facts.
Give me a citation token for the NDVI reading near Mount Fuji.
Verify that this emem:fact token matches the value I am about to report.
Find places similar to this farm plot and show the cell addresses.
listing.setup.h
listing.setup.remote
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http emem https://emem.dev/mcp- Start Claude Code and type
/mcp. emem should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it emem and paste this URL:
https://emem.dev/mcp- Click Add. Its tools appear in the chat's tools menu.
Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
- Check that the URL reads
https://emem.dev/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://emem.dev/mcpas the server URL and choose No authentication.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
Cursor
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"emem": {
"url": "https://emem.dev/mcp"
}
}
}VS Code
Install in VS Code a11y.new_tab
Or from a terminal:
code --add-mcp '{"name":"emem","type":"http","url":"https://emem.dev/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"emem": {
"type": "http",
"url": "https://emem.dev/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"emem": {
"serverUrl": "https://emem.dev/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add emem --url https://emem.dev/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.emem]
url = "https://emem.dev/mcp"Gemini CLI
gemini mcp add --transport http emem https://emem.dev/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.
{
"mcpServers": {
"emem": {
"type": "http",
"url": "https://emem.dev/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://emem.dev/mcp.
listing.faq
Can I paste mcp.tc/i/emem into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://emem.dev/mcp, so your client talks to emem directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does emem need an API key or a sign-in?
No. emem doesn't ask for an account or key.
Is emem a remote or a local server?
Remote. Vortx-AI hosts it at https://emem.dev/mcp, and it speaks Streamable HTTP. There's nothing to install.
What can emem do?
It has 18 tools, including emem_entity, emem_locate and emem_recall. You can resolve a place name or coordinates to a canonical cell64 address, recall signed facts for a place and band, with auto-materialization and mint and resolve emem:fact: citation tokens.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc's robot read emem's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
listing.em.h
listing.em.lead listing.em.how
listing.em.badge
[](https://mcp.tc/i/emem)<a href="https://mcp.tc/i/emem"><img src="https://mcp.tc/i/emem/badge.svg" alt="emem on mcp.tc" height="20"></a>listing.em.badge_note
listing.em.widget
<script src="https://mcp.tc/w/emem.js" async></script>listing.em.widget_note
iframe
<iframe src="https://mcp.tc/embed/emem" title="emem on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>listing.em.iframe_note
listing.disclaimer_checked