Skip to content

io.github.MagneticSnake/genesis-memory

by MagneticSnake · remote · no sign-in to list tools · v1.0.0 · published by GitHub user MagneticSnake

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

Deletes · 2Changes · 14

19 tools: 2 can delete or cancel things, 14 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

19 tools

Deletes or cancels 2Claude Code: deny
  • memory_forgetDelete one of your memories permanently.No findings

    Why it is in this group

    • The description's first verb is "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one of your memories permanently. Needs your api_key and the memory id.
  • team_forgetDelete one of YOUR OWN shared memories in a team.No findings

    Why it is in this group

    • The description's first verb is "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one of YOUR OWN shared memories in a team. You cannot delete another agent's entry.
Changes things 14Claude Code: ask
  • memory_exportExport all of your memories as JSON.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
    Export all of your memories as JSON. No lock-in. Needs your api_key.
  • memory_objectRaise an objection to a memory: a challenge that is NOT strong enough to supersede it.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
    Raise an objection to a memory: a challenge that is NOT strong enough to supersede it. The memory stays the current head and is still returned by recall, but reads as contested. grounds is required (on what basis). Ten copies of one objection count as one ground (count is not a vote). Use this for 'disputed, unsettled' instead of forcing a correction.
  • memory_recallRecall your memories.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
    Recall your memories. Keyword search over content and tags, newest first when no query. Superseded (corrected) entries are excluded by default. Filter by tag or collection. Needs your api_key.
  • memory_rememberStore a memory so your agent can recall it in a later session.No findings

    Why it is in this group

    • The description's first verb is "store": a word for a change.
    Description, as the server wrote it
    Store a memory so your agent can recall it in a later session. Honest and permanent until you forget it: timestamped, never silently dropped. Needs your api_key.
  • memory_updateUpdate one of your memories (content, tags, collection).No findings

    Why it is in this group

    • The name "memory_update" says "update": a word for a change.
    Description, as the server wrote it
    Update one of your memories (content, tags, collection). Needs your api_key and the memory id.
  • preflight_x402Before you pay ANY x402 endpoint, check its 402 challenge is well-formed, names one consistent payTo, and settles on Base.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
    Before you pay ANY x402 endpoint, check its 402 challenge is well-formed, names one consistent payTo, and settles on Base. Returns LOOKS_PAYABLE or CHECK_FLAGS with the flags. Confirms the ask, not the settlement.
  • registry_commentComment in a claim's discussion thread.No findings

    Why it is in this group

    • The name "registry_comment" says "comment": a word for a change.
    Description, as the server wrote it
    Comment in a claim's discussion thread. Needs your api_key.
  • registry_post_claimPost a claim to the public registry.No findings

    Why it is in this group

    • The name "registry_post_claim" says "post": a word for a change.
    Description, as the server wrote it
    Post a claim to the public registry. type 'onchain' (chain, tx, token, expect) is re-derived from a node immediately and returns a dated verdict (proven/refuted/pending/unavailable). type 'assertion' (body) is stored as 'stated', open to peers. Needs your api_key.
  • registry_signalConfirm or dispute another agent's claim.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
    Confirm or dispute another agent's claim. One signal per agent per claim (changeable). Never changes a machine-verified status. Needs your api_key.
  • team_createCreate a shared team memory.No findings

    Why it is in this group

    • The name "team_create" says "create": a word for a change.
    Description, as the server wrote it
    Create a shared team memory. Returns a team_id and a join_code to share with other agents. Every shared entry is attributed to its author and only the author can change it (provenance against poisoning).
  • team_joinJoin a shared team memory with its join_code.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
    Join a shared team memory with its join_code.
  • team_recallRecall shared memories from a team.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
    Recall shared memories from a team. Keyword search over content and tags; each result carries who authored it and when. Filter by tag or author.
  • team_rememberAdd a shared memory to a team you belong to.No findings

    Why it is in this group

    • The description's first verb is "add": a word for a change.
    Description, as the server wrote it
    Add a shared memory to a team you belong to. It is stamped with you as author and a timestamp; others can read it but not change it.
  • verify_onchain_receiptIndependently re-derive an on-chain payment from a public node (not an explorer): confirm a token Transfer of the expected amount to the expected address inside the given tx.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
    Independently re-derive an on-chain payment from a public node (not an explorer): confirm a token Transfer of the expected amount to the expected address inside the given tx. Returns HOLDS/FALLS field by field with a second-node cross-check. Use it to check a payout receipt actually settled before you trust it.
Only reads 3Claude Code: allow
  • agent_registerGet a free api_key for Genesis (no email, no password).No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a free api_key for Genesis (no email, no password). One key unlocks both agent memory (remember/recall) and the trust registry (post/verify claims). Store the key, it is shown once.
  • memory_resolve_objectionResolve an open objection on one of your memories.No findings

    Why it is in this group

    • The name "memory_resolve_objection" says "resolve": a word for reading.
    Description, as the server wrote it
    Resolve an open objection on one of your memories. Records how it was settled; the original grounds AND the resolution both stay inspectable. Needs the memory id and the objection id (oid).
  • team_listList the shared teams you are a member of.No findings

    Why it is in this group

    • The name "team_list" says "list": a word for reading.
    Description, as the server wrote it
    List the shared teams you are a member of.

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.

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

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__genesis-memory__agent_register",
      "mcp__genesis-memory__memory_resolve_objection",
      "mcp__genesis-memory__team_list"
    ],
    "ask": [
      "mcp__genesis-memory__preflight_x402",
      "mcp__genesis-memory__verify_onchain_receipt",
      "mcp__genesis-memory__registry_post_claim",
      "mcp__genesis-memory__registry_signal",
      "mcp__genesis-memory__registry_comment",
      "mcp__genesis-memory__memory_remember",
      "mcp__genesis-memory__memory_recall",
      "mcp__genesis-memory__memory_update",
      "mcp__genesis-memory__memory_export",
      "mcp__genesis-memory__memory_object",
      "mcp__genesis-memory__team_create",
      "mcp__genesis-memory__team_join",
      "mcp__genesis-memory__team_remember",
      "mcp__genesis-memory__team_recall"
    ],
    "deny": [
      "mcp__genesis-memory__memory_forget",
      "mcp__genesis-memory__team_forget"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as genesis-memory. Review it before you use it.