Nuramem MCP Server

by nuramem Your server? Claim it

answering

Nuramem is answering right now. Last checked 12 min ago.

Cross-model memory for people and teams: one memory every AI you use loads at session start.

Uptime history 48 days of history · worst day 96%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

255 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add nuramem --transport http https://mcp.nuramem.ai/mcp

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

https://mcp.nuramem.ai/mcp

~/.codex/config.toml

[mcp_servers.nuramem]
url = "https://mcp.nuramem.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "nuramem": {
      "url": "https://mcp.nuramem.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "nuramem": {
      "type": "http",
      "url": "https://mcp.nuramem.ai/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

URL	Transport	State	Latency	Checked
https://mcp.nuramem.ai/mcp	streamable-http	sign-in	230 ms	12 min ago

Alternatives to Nuramem

same job, measured the same way

TeamShared

by xhad

Shared memory for coding agents. Stop re-explaining your codebase every session.

92 tools answering

Engram

by engram

Memory for AI agent teams across tools, sessions, repositories, and teammates.

230 installs/wk answering

Evc Mesh MCP

by entire-vc

Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.

answering

memsprout

by memsprout

shared AI-context layer for teams — persistent memory your agents search and update over MCP

answering

MCP Locker

by mcplocker

One private endpoint for your MCP servers and skills. Free, Pro & Teams.

answering

Nysa

by usenysa

Shared memory for teams that work with AI agents: meetings, email and calendar in one brain.

answering

Memocore

by memocore

Cloud memory for AI agents and teams — save, search, recall.

answering

Callingly

by callingly

Lets AI agents get leads on the phone: call, send SMS, and schedule callbacks for sales teams.

answering

Nuramem — questions

Answers built from our own checks of this server.

Why is there no tool list for Nuramem?

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

How do I connect Nuramem?

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

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

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