EverMe MCP Server

by evermind-ai Your server? Claim it

answering

EverMe is answering right now. Last checked 14 min ago.

Search personal memories and retrieve context from EverMe.

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

877 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add everme --transport http https://api.everme.evermind.ai/mcp

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

https://api.everme.evermind.ai/mcp

~/.codex/config.toml

[mcp_servers.everme]
url = "https://api.everme.evermind.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "everme": {
      "url": "https://api.everme.evermind.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "everme": {
      "type": "http",
      "url": "https://api.everme.evermind.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://api.everme.evermind.ai/mcp	streamable-http	sign-in	912 ms	14 min ago

Alternatives to EverMe

same job, measured the same way

Hackernews

by pipeworx-io

Hacker News MCP — search and retrieve stories from Hacker News

354 installs/wk 49 tools answering

Recall

by clauderecall

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

local only

Recall

by clauderecallhq

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

167 installs/wk local only

Sensefold

by sensefold

Personal context for every AI: search, read, and write back to your private Markdown library.

answering

Link

by gowtham0992

Local personal memory for agents as MCP tools — remember, recall, search, context, graph traversal.

284 installs/wk local only

prompts.chat MCP Server

by f

Search and retrieve AI prompts from prompts.chat, the social platform for AI prompts.

344 installs/wk local only

Memdata

by thelabvenice

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

47 installs/wk local only

Zdravo Cursor

by zdravo-ai

Persistent AI memory for Cursor. Save and search memories via Zdravo.

68 installs/wk local only

EverMe — questions

Answers built from our own checks of this server.

Why is there no tool list for EverMe?

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

How do I connect EverMe?

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

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

It answers our handshake in 877 ms on average, which is faster than 7% 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.