RecallMax-Neural MCP Server

by evozim Your server? Claim it

answering

RecallMax-Neural is answering right now. Last checked 3 min ago.

Semantic context compression and cognitive memory layer for LLM swarms.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

89 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add recallmax --transport http https://recallmax-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "recallmax": {
      "url": "https://recallmax-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.recallmax]
url = "https://recallmax-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "recallmax": {
      "url": "https://recallmax-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "recallmax": {
      "url": "https://recallmax-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://recallmax-mcp.vercel.app/api/mcp	sse	needs auth	91 ms	3 min ago

Alternatives to RecallMax-Neural

same job, measured the same way

Yantrikdb MCP

by yantrikos

Cognitive memory for AI agents — semantic recall, knowledge graph, and contradiction detection

1 446 installs/wk local only

Claude Memory Manager

by nyxtoolsdev

Cross-session memory for Claude Code — context capture, semantic search, recall

80 installs/wk local only

Cap Shield

by robinlidberg-dot

Context selection and compression for AI agents - recall measured, not claimed.

217 installs/wk local only

Engram Cc

by morous-dev

Universal AI coding assistant memory — session handoff, SLM compression, and semantic retrieval.

38 installs/wk local only

Longhand

by wynelson94

Local memory for Claude Code. Semantic recall across session history with zero API calls.

244 installs/wk local only

Recall

by clauderecallhq

Persistent memory for Claude Code. Search, recall, and re-inject context from any session.

430 installs/wk local only

Recall

by clauderecall

Persistent memory for Claude Code. Search, recall, and re-inject context from any session.

local only

Memdata

by thelabvenice

Persistent memory for AI agents. Store context, retrieve it semantically.

37 installs/wk local only

RecallMax-Neural — questions

Answers built from our own checks of this server.

Why is there no tool list for RecallMax-Neural?

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

How do I connect RecallMax-Neural?

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 will need your own credentials: it refuses anonymous clients.

Does RecallMax-Neural need an API key?

Yes. Every time we knock, RecallMax-Neural answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is RecallMax-Neural?

It answers our handshake in 89 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.