mcpbeat Sign in

Bench47 MCP Server

answering

Bench47 is answering right now. Last checked 13 min ago.

Shared Markdown memory for your agents: docs, typed collections, files, skills and Dispatch.

Uptime history 49 hours of history
49 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
170 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Bench47 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 13 min ago.

run in your terminal
claude mcp add bench47 --transport http https://api.bench47.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.bench47.com/mcp
~/.codex/config.toml
[mcp_servers.bench47]
url = "https://api.bench47.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "bench47": {
      "url": "https://api.bench47.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "bench47": {
      "type": "http",
      "url": "https://api.bench47.com/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.bench47.com/mcp streamable-http sign-in 153 ms 13 min ago

Alternatives to Bench47

same job, measured the same way
Bench47
by markbase

Shared Markdown memory for your agents: docs, typed collections, files, skills and Dispatch.

answering
Korpus
by korpus

Shared memory for teams and their AI agents: Markdown concepts with typed links in shared bundles.

answering
Glen
by tryglen

Search your team's shared agent memory, and use and save the org's skills and documents.

answering
Vibsync
by vibsync

One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.

answering
Vortex Notes
by vortex-303

E2E-encrypted markdown notes as shared memory for you and your agents, with local semantic search.

279 installs/wk local only
Agent Memory MCP
by xultrax-web

Markdown memory for AI agents. Files you can read, edit, grep, and commit. Not a database.

466 installs/wk local only
What's Loaded
by stcmain

What fills your agent's context window before a session starts: skill descriptions, memory files.

78 installs/wk local only
Bilg
by bilgai

Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.

answering

Bench47 — questions

Answers built from our own checks of this server.

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