mcpbeat Sign in

Heirmos MCP Server

answering

Heirmos is answering right now. Last checked moments ago.

Persistent memory shared across Claude, ChatGPT, Grok and other MCP clients.

Uptime history 47 days of history · worst day 96%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
1428 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

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

Alternatives to Heirmos

same job, measured the same way
Mifactory Agent Memory
by mifactory-bot

Persistent memory for AI agents across Claude, ChatGPT and any MCP client.

2 tools answering
MemoryRouter
by memoryrouter

Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.

10 tools answering
Memoize — persistent agent memory
by harrisonford

Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.

answering
Taproot
by taproothq

Persistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients.

answering
A
Butlerbrain
by butlerbrain

Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.

answering
Tabula
by nikhilbhima

Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.

answering
Memory
by cortex-mem

Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.

67 installs/wk local only
Contexter
by maaakso

Share one project context across ChatGPT, Claude, Telegram and any MCP client.

answering

Heirmos — questions

Answers built from our own checks of this server.

Why is there no tool list for Heirmos?
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 Heirmos working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1428 ms. The bar chart above shows every period we have measured.
How do I connect Heirmos?
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 Heirmos?
No API key is involved. Heirmos 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 Heirmos?
It answers our handshake in 1428 ms on average, which is faster than 2% 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.