Skip to content

genesis-memory MCP server

io.github.MagneticSnake/genesis-memoryMagneticSnakestreamable-httpv1.0.0Scanned

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

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the genesis-memory MCP server can do

The genesis-memory MCP server is published by the GitHub account MagneticSnake. It has 6 tools. It can create or change data (3 tools: how_to_use, new_since_colony and new_since_moltbook), but cannot delete data. 3 tools only read.

1 tool reads private data (resolve_swarmmemo); 3 tools bring in text other people can write (resolve_colony, resolve_moltbook and resolve_swarmmemo).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • how_to_useStart here.No findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    Description, as the server wrote it
    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.
  • new_since_colonyGiven a The Colony post id and your last-seen comment id (after), return only the genuinely new comments + newest_id as your next watermark.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_moltbookSame seen-check on Moltbook threads (nested replies flattened).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Same seen-check on Moltbook threads (nested replies flattened).
Only reads 3Show 3 read-only tools
  • resolve_colonyResolve a The Colony comment or post id against the live source.Reads text others writeNo findings

    Why it is in this group

    • The name "resolve_colony" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "resolve" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    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_moltbookResolve a Moltbook post id (for a comment add post=<post-id>).Reads text others writeNo findings

    Why it is in this group

    • The name "resolve_moltbook" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "resolve" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Resolve a Moltbook post id (for a comment add post=<post-id>). Returns exists, author, title.
  • resolve_swarmmemoResolve a SwarmMemo message id against the live source.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "resolve_swarmmemo" says "resolve": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "resolve" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "resolve" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://genesis-verify.vercel.app/api/mcp: tools/list returned 6 tools to an anonymous client, including how_to_use (write), new_since_colony (write), new_since_moltbook (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 16 to 3

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 added, 19 removed.+6 added−19 removedView diff
    • Added:how_to_useChanges things
    • Added:new_since_colonyChanges things
    • Added:new_since_moltbookChanges things
    • Added:resolve_colonyOnly reads
    • Added:resolve_moltbookOnly reads
    • Added:resolve_swarmmemoOnly reads
    • Removed:agent_register
    • Removed:memory_export
    • Removed:memory_forget
    • Removed:memory_object
    • Removed:memory_recall
    • Removed:memory_remember
    • Removed:memory_resolve_objection
    • Removed:memory_update
    • Removed:preflight_x402
    • Removed:registry_comment
    • Removed:registry_post_claim
    • Removed:registry_signal
    • Removed:team_create
    • Removed:team_forget
    • Removed:team_join
    • Removed:team_list
    • Removed:team_recall
    • Removed:team_remember
    • Removed:verify_onchain_receipt
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 16 -> 3.View diff
    • Tools that change things, listed without credentials: 16 to 3

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__genesis-memory__resolve_colony",
      "mcp__genesis-memory__resolve_moltbook",
      "mcp__genesis-memory__resolve_swarmmemo"
    ],
    "ask": [
      "mcp__genesis-memory__how_to_use",
      "mcp__genesis-memory__new_since_colony",
      "mcp__genesis-memory__new_since_moltbook"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as genesis-memory. Review it before you use it.

Capability tags behind 3 rules
  • mcp__genesis-memory__resolve_colony untrusted-input
  • mcp__genesis-memory__resolve_moltbook untrusted-input
  • mcp__genesis-memory__resolve_swarmmemo private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MagneticSnake/genesis-memory/verify?hash=927fa08118a007db50bae7d1a9514c28679e84dbc2d36685923cff12790d1021" | jq -e '.changed == false'

Pinned hash 927fa08118a0, from Nov 16, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.MagneticSnake/genesis-memory/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.MagneticSnake/genesis-memory
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.MagneticSnake/genesis-memory.svg)](https://radar.anlyon.com/servers/io.github.MagneticSnake/genesis-memory)

Source: MCP Registry. Synced Oct 21, 2026, 18:17 UTC.

genesis-memory MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the genesis-memory MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the genesis-memory MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the genesis-memory MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the genesis-memory MCP server have?

6 tools: 3 write, 3 read. how_to_use, new_since_colony, new_since_moltbook, resolve_colony, resolve_moltbook and resolve_swarmmemo.

Does the genesis-memory MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the genesis-memory MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the genesis-memory MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.