mcpbeat Sign in

Memocore MCP Server

answering

Memocore is answering right now. Last checked 13 min ago.

Shared memory for all your AI agents, your whole team and every MCP client — save, search, recall.

Uptime history 49 days of history · worst day 76%
49 days agonow
82.2%
Uptime 24h
74 of 90 checks
Tools
hidden behind auth
1919 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Memocore does not always answer

Over the last week it answered 94.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 13 min ago.

run in your terminal
claude mcp add mcp --transport http https://memocore.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://memocore.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://memocore.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://memocore.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://memocore.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

URLTransportStateLatencyChecked
https://memocore.ai/mcp streamable-http sign-in 1306 ms 13 min ago

Alternatives to Memocore

same job, measured the same way
WorkingMemory
by workingmemory

Persistent personal memory for AI assistants — save, search, and recall across every MCP client.

4 tools answering
memsprout
by memsprout

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

answering
WitWiki
by witwiki

A shared team wiki your coding agents read and write — across every repo and every MCP client.

answering
Agentage Memory
by agentage

One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.

answering
AiAkiv Memory
by aiakiv

Shared long-term memory for AI agents: save and recall context as a searchable knowledge graph.

answering
TeamShared
by xhad

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

92 tools answering
Vibsync
by vibsync

One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.

answering
I
MemVault MCP Server
by dreamor

Shared memory router for AI agents: save/search/recall, session-start injection, review inbox.

local only

Memocore — questions

Answers built from our own checks of this server.

Why is there no tool list for Memocore?
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: 82.2% of checks in the last 24 hours got a reply.
Is Memocore working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 74 of 90 checks got a reply (82.2%), average response time 1919 ms. The bar chart above shows every period we have measured.
How do I connect Memocore?
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 Memocore?
No API key is involved. Memocore 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.