INDIVIDUAL MCP TOOL
emem_recall
Read the signed facts at a canonical address (cell64); auto-materializes on a miss for any band with a registered materializer.
LIVE ENDPOINT
https://emem.dev/mcp
Connect to this endpoint to inspect the live schema for emem_recall and invoke it with your own arguments.
Indexed input schema
{}Risk classification
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.
Parent server
CONNECT WITH APPROVAL
Client installation
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.
Related tools
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_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_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_memory_token_resolve— Parse a `emem:fact:<cell64>:<fact_cid>` citation handle and return the reading it cites.emem_verify_receipt— Verify a signed receipt envelope server-side: rebuilds the canonical preimage under the rule the receipt's OWN `preimage_version` names (v2, current: tagged length-prefixed segments plus a segment binding the inclusion proof; v1: the same without that segment; absent/0: the legacy `request_id | served_at | primitive | cells, | fact_cids,` concatenation), runs ed25519 over the embedded pubkey + signature, and returns `{valid, reason, failure_detail, signature_valid, merkle_proof_valid, signer_pubkey_b32, preimage_blake3_hex}`.emem_memory_contradictions— Surface where the corpus DISAGREES with itself (algebra: competing evidence).emem_guard_verdict— Run emem-guard's policy pipeline over text you are about to send, against this responder's corpus.emem_tools— The map of emem's tool surface, and the only tool you need to find the rest.