Engram MCP Server

by rootcause Your server? Claim it

answering

Engram is answering right now. Last checked 15 min ago.

A second brain for Claude: remembers your work, plans your day, encrypted under a key only you hold.

Uptime history 16 days of history

16 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

327 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Engram every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add engram --transport http https://engram.rootcause.ro/mcp/directory

Settings → Connectors → Add custom connector, then paste this address

https://engram.rootcause.ro/mcp/directory

~/.codex/config.toml

[mcp_servers.engram]
url = "https://engram.rootcause.ro/mcp/directory"

.cursor/mcp.json

{
  "mcpServers": {
    "engram": {
      "url": "https://engram.rootcause.ro/mcp/directory"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "engram": {
      "type": "http",
      "url": "https://engram.rootcause.ro/mcp/directory"
    }
  }
}

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

URL	Transport	State	Latency	Checked
https://engram.rootcause.ro/mcp/directory	streamable-http	sign-in	269 ms	15 min ago

Alternatives to Engram

same job, measured the same way

Pyunto Diary

by pyunto

Read, search and write your encrypted Pyunto diary from Claude. Decrypts only on your own machine.

157 installs/wk local only

Workday MCP

by chrischall

Read-only Workday for Claude — fetch tasks, pay, benefits via your signed-in session

401 installs/wk local only

Octopad

by octopad

The AI brain for builders: ChatGPT, Claude and your other AIs share one workspace and one method.

answering

Huddle

by kfiram

One encrypted chat for you, your people and your AI agents: Claude, Codex, Gemini, Goose.

answering

Geistra

by geistra

Shared memory for your AI apps: Spaces of records, files and plans you and others can work in.

answering

AIm Workout Journal

by aim-journal

Chat forgets your workouts. AIm remembers them for Claude and ChatGPT: sets, weights, 1RM, volume.

answering

Dear User

by bleedmode

Tells you how you and your Claude agent actually work together. Local-only, no API keys.

63 installs/wk local only

Whoop MCP

by souravpn

MCP server for WHOOP — gives Claude access to your recovery, sleep, strain, and workout data

40 installs/wk local only

Engram — questions

Answers built from our own checks of this server.

Why is there no tool list for Engram?

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 Engram 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 327 ms. The bar chart above shows every period we have measured.

How do I connect Engram?

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 Engram?

No API key is involved. Engram 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 Engram?

It answers our handshake in 327 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.