mcpbeat Sign in

Recall MCP Server

answering

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

Notes, files, GitHub, and Drive through one MCP connection.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 63 days of history · worst day 93%
63 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
243 ms
Response time
average over 24h
authentication required
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

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 6 min ago.

run in your terminal
claude mcp add recall --transport http https://recall.arraybud.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://recall.arraybud.app/api/mcp
~/.codex/config.toml
[mcp_servers.recall]
url = "https://recall.arraybud.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "recall": {
      "url": "https://recall.arraybud.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "recall": {
      "type": "http",
      "url": "https://recall.arraybud.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://recall.arraybud.app/api/mcp streamable-http needs auth 111 ms 6 min ago

Alternatives to Recall

same job, measured the same way
dylog
by imjakezimmer32

Notes, files, GitHub, and Drive through one MCP connection.

answering
TalkMill
by imjakezimmer32

Notes, files, GitHub, and Drive through one MCP connection.

answering
Colab Drive MCP
by yummytastycode

Synchronize Colab notebook files through Google Drive without executing notebook code.

127 installs/wk local only
Qualien MCP
by qualienai

MCP gateway for QA/SDET work: Playwright, files, GitHub, Jira, Postgres & more in one connection.

40 installs/wk local only
CI Guard MCP
by carelessdept

Local-first static repository security and configuration drift auditor (CLI, GitHub Action & MCP).

45 installs/wk local only
ClawLink
by claw-link

MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.

answering
MCP Compiler MCP
by robertoyanguas-ops

Audits any live MCP server URL or GitHub repo on Glama's 6-dimension TDQS rubric and compiles drop

2 tools answering
GitHub
by github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

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 91 of 91 checks got a reply (100.0%), average response time 243 ms. The bar chart above shows every period we have measured.
Is Recall still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
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 in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Recall need an API key?
Yes. Every time we knock, Recall answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Recall?
It answers our handshake in 243 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.