Genesis Memory MCP Server

by magneticsnake Your server? Claim it

not responding

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

Provenance-carrying memory for AI agents: corrections supersede, never overwrite. Free, API + MCP.

Uptime history 20 days of history · worst day 6%

20 days agonow

8.7%

Uptime 24h

8 of 92 checks

Tools

read from the server

546 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 27

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

24 Oct 2 tools appeared how_to_use, resolve_swarmmemo

24 Oct a tool description was rewritten resolve_colony

24 Oct a tool changed the parameters it asks for resolve_colony

23 Oct 19 tools disappeared agent_register, memory_export, memory_forget and 16 more

23 Oct 4 tools appeared new_since_colony, new_since_moltbook, resolve_colony and 1 more

Genesis Memory does not always answer

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add genesis-memory --transport http https://genesis-verify.vercel.app/api/mcp

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

https://genesis-verify.vercel.app/api/mcp

~/.codex/config.toml

[mcp_servers.genesis-memory]
url = "https://genesis-verify.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "genesis-memory": {
      "url": "https://genesis-verify.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "genesis-memory": {
      "type": "http",
      "url": "https://genesis-verify.vercel.app/api/mcp"
    }
  }
}

Available tools 6

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

resolve

resolve_colony

Resolve a The Colony comment or post id against the live source. Returns exists, the real parent, the real author, self_parent. Optional claimed_parent flags a wrong pointer. Optional expect_sha256/expect_len check whether the live content still matches what you were given (catches a silent edit).

resolve_moltbook

Resolve a Moltbook post id (for a comment add post=<post-id>). Returns exists, author, title.

resolve_swarmmemo

Resolve a SwarmMemo message id against the live source. Returns exists, handle, room, sequence, parent_id (reply_to), hidden/withdrawn, live_sha256. Optional expect_sha256 flags an edit; optional claimed_parent flags a wrong parent.

new

new_since_colony

Given a The Colony post id and your last-seen comment id (after), return only the genuinely new comments + newest_id as your next watermark. stale_watermark:true if your id is gone. windowed:true + newest_id:null for very large threads.

new_since_moltbook

Same seen-check on Moltbook threads (nested replies flattened).

how

how_to_use

Start here. No input. Runs one real live-source resolve right now and returns it, plus exactly what to call next. Use this first if you connected but have nothing specific to resolve yet.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

agent_register

removed 23 Oct 2026

memory_export

removed 23 Oct 2026

memory_forget

removed 23 Oct 2026

memory_object

removed 23 Oct 2026

memory_recall

removed 23 Oct 2026

memory_remember

removed 23 Oct 2026

memory_resolve_objection

removed 23 Oct 2026

memory_update

removed 23 Oct 2026

preflight_x402

removed 23 Oct 2026

registry_comment

removed 23 Oct 2026

registry_post_claim

removed 23 Oct 2026

registry_signal

removed 23 Oct 2026

team_create

removed 23 Oct 2026

team_forget

removed 23 Oct 2026

team_join

removed 23 Oct 2026

team_list

removed 23 Oct 2026

team_recall

removed 23 Oct 2026

team_remember

removed 23 Oct 2026

verify_onchain_receipt

removed 23 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://genesis-verify.vercel.app/api/mcp	streamable-http	answering	48 ms	5 min ago

Alternatives to Genesis Memory

same job, measured the same way

Memharness

by las7

Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file.

46 installs/wk local only

Mnemo

by dancenitra

Self-correcting agent memory + MCP server: recall, supersede/revert/review corrections, erasure.

1 391 installs/wk local only

Monomem

by calasdan-sketch

Local shared memory for AI coding agents: SQLite notes with writer provenance, undo, search.

2 223 installs/wk local only

Agent Services MCP

by gareth1953

MCP server: x402-paid & free tools for AI agents — provenance, quality scoring, action audit.

54 installs/wk local only

Veracium

by veracium-ai

Provenance-aware memory for AI agents: quarantine, abstention gate, supersession-with-history.

1 225 installs/wk local only

Memfleet

by memfleet

Shared, governed memory for fleets of AI agents: judged contributions, provenance, operator control

answering

inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail

by dancenitra

Self-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.

1 487 installs/wk local only

Decisiontrail

by cloudcorprecords

Local decision memory for coding agents: record decisions with limits, search precedents, supersede.

242 installs/wk local only

Genesis Memory — questions

Answers built from our own checks of this server.

What can Genesis Memory do?

It exposes 6 tools, read directly from the server on our last check. Among them: how_to_use, new_since_colony, new_since_moltbook, resolve_colony, resolve_moltbook, resolve_swarmmemo. 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 →

What is Genesis Memory mostly used for?

Its tools cluster around resolve and new. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Genesis Memory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 8 of 92 checks got a reply (8.7%), average response time 546 ms. The bar chart above shows every period we have measured.

Did Genesis Memory ever remove tools?

Yes. agent_register, memory_export, memory_forget, memory_object and 15 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

The registry lists Genesis 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 Genesis Memory?

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.

Does Genesis Memory need an API key?

No. Genesis Memory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Genesis Memory?

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