mcpbeat Sign in

Mem.Center MCP Server

answering

Mem.Center is answering right now. Last checked 2 min ago.

Read-only memory search and task context for AI clients. Requires a Mem.Center Pro account.

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

Nothing serious here today

Today is the operative word: we check Mem.Center 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 2 min ago.

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

Alternatives to Mem.Center

same job, measured the same way
SkillDB
by devchad-cmd

Search and load AI agent skills. Free metadata; full content requires a Pro or Studio account.

145 installs/wk answering
ContextStream MCP Server
by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

913 installs/wk local only
Waspy
by waspytech

Search contacts, read chats, and send confirmed messages for one Waspy account.

answering
R
Raconteur AI Gateway
by getbotlens

MCP gateway for raconteur.com: articles, search and full text. Read-only, no auth.

6 tools answering
TopClozer LinkedIn MCP
by topclozer

LinkedIn for AI agents: search people, read profiles, posts and connections via a connected account

answering
ORANO Personal Context MCP
by manuvamp

Read-only MCP server: let AI agents read your ORANO saved-video library, tasks, and memory.

answering
MaximoFN Content
by maximofn

Read-only search over the AI/ML posts, tips and projects of maximofn.com (es/en/pt).

3 tools answering
Verbasil, company memory
by verbasil

Company memory for your team and its AI agents. Hosted service, account required.

answering

Mem.Center — questions

Answers built from our own checks of this server.

Why is there no tool list for Mem.Center?
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 Mem.Center 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 355 ms. The bar chart above shows every period we have measured.
How do I connect Mem.Center?
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 Mem.Center?
No API key is involved. Mem.Center 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 Mem.Center?
It answers our handshake in 355 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.