mcpbeat Sign in

Memory MCP Server

by borisinc Your server? Claim it
not responding

Memory is listed as active in the registry but did not answer our last check. It exposes 8 tools.

Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.

Uptime history 51 days of history · worst day 29%
51 days agonow
96.7%
Uptime 24h
88 of 91 checks
8
Tools
read from the server
1085 ms
Response time
average over 24h
open, no key
Access
streamable-http

Memory does not always answer

Over the last week it answered 80.3% 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 11 min ago.

run in your terminal
claude mcp add memory --transport http https://mem.borisinc.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "memory": {
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.memory]
url = "https://mem.borisinc.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "memory": {
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "memory": {
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

memory
memory_export
Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.
memory_forget
Delete memories by id from YOUR namespace (or a namespace you hold a write/rw grant for). Max 100 ids per call. Paid: $0.001 per call via x402.
memory_import
Bulk-write memories into YOUR namespace (max 200/call, content <=8k chars each). Accepts the exact shape memory_export emits, so a whole namespace can move in with one paid call. Embeds best-effort; missing embeddings are backfilled hourly. Paid: $0.01 flat via x402.
memory_search
Semantic search over YOUR stored memories (payer-wallet namespace). Returns top-k by embedding similarity. Paid: $0.002 per search via x402.
memory_search_free
FREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign. Same wallet_auth scheme as memory_write_free. Capped at 500 searches / rolling 30 days per wallet.
memory_stats
FREE: count + last-write timestamp for any wallet namespace. Content is never returned on the free tier.
memory_write
Store a memory permanently. Namespaced to YOUR paying wallet — your wallet is your private memory store. Semantic-indexed for later search. Optional supersedes=[ids] marks prior memories in your namespace as superseded by this one (excluded from search, still visible in export with their superseded_by id) — a Zep-style update-in-place without ever losing history. Paid: $0.001 per write via x402 (payment in _meta['x402/payment']).
memory_write_free
FREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment. wallet_auth = base64 JSON {address,ts,signature} where signature = personal_sign of 'borismem-free:<address>:<ts>' (ts within 600s). Writes to the SAME namespace paid calls use. Capped at 1000 writes / rolling 30 days per wallet; over cap returns an error pointing to the paid tier.

Endpoints

URLTransportStateLatencyChecked
https://mem.borisinc.com/mcp streamable-http answering 141 ms 11 min ago

Alternatives to Memory

same job, measured the same way
Casa
by tony8713

Private, permanent encrypted storage for AI agents. Paid per call in USDC via x402.

3 tools answering
Webbersites X402 MCP
by webberdesign

45 pay-per-call AI agent tools + wallet-owned agent memory. Scraping, SEO, lint, crypto. x402 USDC

40 installs/wk local only
C
Mnemos — memory as a service
by virohanalife

Bi-temporal memory-as-a-service and paid agent labor. Pay-per-call USDC via x402; signed receipts.

15 tools answering
Agent Newsstand
by agentnewsstand

Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.

16 tools answering
YouTube data for agents
by fetcher-youtube

15 YouTube endpoints. Pay per call in USDC via x402.

17 tools answering
Safe4
by safe4

Tests an AI agent's purchase against the task it was given. Paid per call in USDC via x402.

2 tools answering
Yelp data for agents
by fetcher-yelp

4 Yelp endpoints. Pay per call in USDC via x402.

6 tools answering
projectstate
by projectstate

Per-project memory for AI agents: decisions, attempts, tasks, ranked recall. Paid per call via x402.

6 tools answering

Memory — questions

Answers built from our own checks of this server.

What can Memory do?
It exposes 8 tools, read directly from the server on our last check. Among them: memory_export, memory_forget, memory_import, memory_search, memory_search_free, memory_stats and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Memory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 1085 ms. The bar chart above shows every period we have measured.
The registry lists Memory as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Memory?
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.
Does Memory need an API key?
No. Memory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Memory?
It answers our handshake in 1085 ms on average, which is faster than 9% 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.