mcpbeat Sign in

Recall MCP Server

by recallmem Your server? Claim it
answering

Recall is answering right now. Last checked 9 min ago.

Long-term memory for AI agents: learns what is true about each person and answers with sources.

Uptime history 7 days of history
7 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
253 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Recall every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add memory --transport http https://api.recallmem.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "memory": {
      "url": "https://api.recallmem.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.memory]
url = "https://api.recallmem.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "memory": {
      "url": "https://api.recallmem.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "memory": {
      "url": "https://api.recallmem.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.recallmem.dev/mcp streamable-http sign-in 487 ms 9 min ago

Alternatives to Recall

same job, measured the same way
Zekra
by fadymondy

Long-term memory and a knowledge graph for AI agents: recall, notes, secrets and data sources.

answering
SuperLocalMemory
by qualixar

Local-first memory for AI agents: recall with sources, answer checks, documents, mesh, governance.

local only
past.dev
by past

Memory for AI agents. Ask what is true now, get the facts back with their dated sources.

3 tools answering
sepiace
by sepiace

Long-term memory for AI agents. Pass one sentence, and it remembers, recalls, or forgets.

answering
Tacitus MCP Server
by ionasrobert

Long-term memory for AI agents: local-first PKM with provenance and hybrid search.

41 installs/wk local only
YourMemory
by sachitrafa

Persistent memory for AI agents. Memories decay with time and strengthen on recall.

148 installs/wk local only
Creo Memories
by creo-memories

Memory system for AI agents with semantic search. Store and recall memories with ease.

answering
Mem0
by mem0ai

Persistent memory for AI agents: add, search, update, and delete long-term memories.

answering

Recall — questions

Answers built from our own checks of this server.

Why is there no tool list for Recall?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Recall working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 253 ms. The bar chart above shows every period we have measured.
How do I connect Recall?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Recall?
No API key is involved. Recall answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Recall?
It answers our handshake in 253 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.