mcpbeat Sign in

Beep MCP Server

answering

Beep is answering right now. Last checked 11 min ago.

Shared memory for AIs. Share a project with anyone and their AI knows everything yours does.

Uptime history 10 days of history · worst day 99%
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
404 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Beep missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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

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

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://mcp.getbeep.app streamable-http sign-in 401 ms 11 min ago

Alternatives to Beep

same job, measured the same way
Hilbana
by hilbana

Project tracker for teams working with AI agents: issues, cycles, docs and shared agent memory.

answering
MemoryComb
by bryceblackroot

One memory for every AI: Claude, ChatGPT and more share a memory that lives on your computer.

local only
Atlaso Memory
by atlaso

Atlaso, the AI memory layer: one shared, persistent memory for every AI tool you connect.

answering
Unabyss
by unabyss

Shared memory for every AI tool you use.

answering
Agentics
by agenticstechnologies

Shared memory for AI agents, with a receipt for every write. Hosted MCP at agentics.you/mcp.

answering
emem, the verifiable memory protocol for the physical world
by vortx-ai

Shared, verifiable memory for machines and AI. Encode where data lives; decode with any AI.

18 tools answering
AiNecto
by ainecto

Shared project memory for people and AI agents: workspaces, documents, ERD, diagrams and boards.

answering
Kijito
by kijito

Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.

answering

Beep — questions

Answers built from our own checks of this server.

Why is there no tool list for Beep?
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 Beep 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 404 ms. The bar chart above shows every period we have measured.
How do I connect Beep?
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 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 Beep?
No API key is involved. Beep 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 Beep?
It answers our handshake in 404 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.