INDIVIDUAL MCP TOOL

emem_memory_token_resolve

Parse a `emem:fact:<cell64>:<fact_cid>` citation handle and return the signed fact body the cid binds.

emem.devnone authenticationAvailability not checked

Input schema

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.emem]
url = "https://emem.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: emem
Remote MCP URL: https://emem.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "emem": {
      "url": "https://emem.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "emem",
  "transport": "streamable-http",
  "url": "https://emem.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

emem_tools — The map of emem's tool surface, and the only tool you need to find the rest.
emem_locate — Mint the canonical, vendor-neutral address (cell64) for a real-world place: the shared spatial identity every agent resolves to identically, so two models refer to the same ground instead of two descriptions of it.
emem_ask — Single-shot free-text answer about a real-world location, backed by signed satellite/elevation/water/built-up receipts.
emem_memory_token — Mint a citation handle, `emem:fact:<cell64>:<fact_cid>` (or `:<state_cid>`), that any agent or LLM resolves to the byte-identical signed object.
emem_echo_verify — Grade a value you are about to emit against the signed fact your citation points at.
emem_memory_bundle — Compose N (cell, band, tslot?
emem_entity — Give a real-world object (a bridge, a farm plot, a river, a named place) a single, shared, content-addressed identity that any agent resolves the same way.
emem_entity_resolve — Converge a fuzzy phrasing onto the canonical object other agents already minted, so everyone co-refers to the same identity instead of re-minting divergent ones.