mcpbeat Sign in

Armbrain MCP Server

by benfinklea Your server? Claim it
answering

Armbrain is answering right now. Last checked 2 min ago.

AI memory layer for fractional CMOs -- client-partitioned minds, meeting prep, and EOS.

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

Uptime history 47 days of history · worst day 97%
47 days agonow
97.8%
Uptime 24h
89 of 91 checks
—
Tools
hidden behind auth
1419 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Armbrain does not always answer

Over the last week it answered 98.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 2 min ago.

run in your terminal
claude mcp add armbrain --transport http https://api.armbrain.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "armbrain": {
      "url": "https://api.armbrain.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.armbrain]
url = "https://api.armbrain.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "armbrain": {
      "url": "https://api.armbrain.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "armbrain": {
      "url": "https://api.armbrain.io/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.armbrain.io/mcp streamable-http sign-in 1362 ms 2 min ago

Alternatives to Armbrain

same job, measured the same way
Minutes
by silverstein

The private, owned conversation-memory layer for AI. Record, transcribe, and search every meeting.

238 installs/wk local only
Brains
by brainsforai

Personal wiki and memory layer for AI assistants. Persistent, structured memory across sessions.

answering
Koda
by aabxtract

Verification and memory layer for coding-agent workflows.

39 installs/wk local only
Agent Memory MCP
by ipiton

Memory, docs, and repo context layer for engineering agents.

local only
MemoraEU
by pquattro

Zero-knowledge persistent memory layer for AI agents. Encrypted client-side, hosted in France.

local only
Gitmem
by gitmem-dev

Persistent institutional memory for AI coding agents. Memory that compounds.

99 installs/wk local only
Memini
by lumayapartners

Local-first project memory and mistake-prevention guardrails for AI coding agents.

42 installs/wk local only
Engram
by kael-bit

Hierarchical memory for AI agents. Three-layer (buffer/working/core) with decay and promotion.

30 installs/wk local only

Armbrain — questions

Answers built from our own checks of this server.

Why is there no tool list for Armbrain?
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: 97.8% of checks in the last 24 hours got a reply.
Is Armbrain working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 1419 ms. The bar chart above shows every period we have measured.
Is Armbrain 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 Armbrain?
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 Armbrain?
No API key is involved. Armbrain 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 Armbrain?
It answers our handshake in 1419 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.