Home / MCP registry index / app.getbeep/beep
Beep
app.getbeep/beep in the official MCP registry.
Endpoint https://mcp.getbeep.app/.
The registry describes it as: Shared memory for AIs. Share a project with anyone and their AI knows everything yours does.
On 2026-10-27 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-getbeep-beep)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Memory and knowledge MCP servers
| pg.ddx.io: the PostgreSQL community's memory io.ddx.pg/archive | 125 tools, nothing matched 2026-10-27 |
| AgentMart ai.ciphyr.agentmart/agentmart | 112 tools, nothing matched 2026-10-21 |
| Wicked MCP io.github.choaticpixels/wicked-mcp | 108 tools, nothing matched 2026-10-26 |
| Wicked MCP io.github.WickedAPI/wicked-mcp | 108 tools, nothing matched 2026-10-27 |
| io.github.webberdesign/webbersites-x402-data-api io.github.webberdesign/webbersites-x402-data-api | 78 tools, nothing matched 2026-10-22 |
| Tincan com.gotincan/tincan | 62 tools, nothing matched 2026-10-27 |