mcpbeat Sign in

MayaMemo MCP Server

answering

MayaMemo is answering right now. Last checked 3 min ago.

Evidence-backed project memory and checkpoints for AI coding agents.

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

Nothing serious here today

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

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

Alternatives to MayaMemo

same job, measured the same way
Mindpm
by umitkavala

Project memory and a control plane for AI coding agents.

85 installs/wk local only
Aletheia
by firatmio

Project memory for coding agents whose memories carry code evidence, re-checked on every recall.

local only
KnowledgeRail
by deviank88

Persistent, evidence-backed project knowledge and task context for coding agents.

local only
Sinter
by shellfu

Persistent, evidence-backed code graph for coding agents.

545 installs/wk local only
Contextful
by inferensys

Efficient context management: code search, evidence packs, and memory for coding agents.

16 installs/wk local only
I
ITHZ MCP
by ithz

Local deterministic project memory for AI agents with context packs, gates and checkpoints.

125 installs/wk local only
Provena Agent Memory
by admiralpunk

Self-hosted MCP memory for AI agents: persistent context with evidence-backed claims.

365 installs/wk local only
Memini
by lumayapartners

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

18 installs/wk local only

MayaMemo — questions

Answers built from our own checks of this server.

Why is there no tool list for MayaMemo?
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 MayaMemo 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 873 ms. The bar chart above shows every period we have measured.
How do I connect MayaMemo?
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 MayaMemo?
No API key is involved. MayaMemo 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 MayaMemo?
It answers our handshake in 873 ms on average, which is faster than 9% 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.