io.github.MagneticSnake/genesis-memory
REMOTE · GENESIS-VERIFY.VERCEL.APP
Provenance-carrying memory for AI agents: corrections supersede, never overwrite. Free, API + MCP.
Available components
Last scanned (17 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 399 tokens (~66/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 16 days we've observed: 17 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
- Tool “resolve_colony” rewrote its description, which is the text the model reads security
- Schema quality: 55 → 66 ▼ functional
- Schema quality: fair → good functional
- New tool “how_to_use” functional
- New tool “resolve_swarmmemo” functional
- “resolve_colony” added an optional parameter “expect_len” cosmetic
- “resolve_colony” added an optional parameter “expect_sha256” cosmetic
- 23 Oct 26 −1
- Stability: 0.10 → fail ▼ security
- Tool “agent_register” was removed ▼ security
- Tool “memory_export” was removed ▼ security
- Tool “memory_forget” was removed ▼ security
- Tool “memory_object” was removed ▼ security
- Tool “memory_recall” was removed ▼ security
- Tool “memory_remember” was removed ▼ security
- Tool “memory_resolve_objection” was removed ▼ security
- Tool “memory_update” was removed ▼ security
- Tool “preflight_x402” was removed ▼ security
- Tool “registry_comment” was removed ▼ security
- Tool “registry_post_claim” was removed ▼ security
- Tool “registry_signal” was removed ▼ security
- Tool “team_create” was removed ▼ security
- Tool “team_forget” was removed ▼ security
- Tool “team_join” was removed ▼ security
- Tool “team_list” was removed ▼ security
- Tool “team_recall” was removed ▼ security
- Tool “team_remember” was removed ▼ security
- Tool “verify_onchain_receipt” was removed ▼ security
- The server changed its declared name: genesis-verify → genesis-resolver security
- Tool coverage: 44% → 0% ▼ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: good → fair functional
- Destructive annotations: 0 → pass functional
- Server version: 1.0.0 → 2.0.0 functional
- New tool “new_since_colony” functional
- New tool “new_since_moltbook” functional
- New tool “resolve_colony” functional
- New tool “resolve_moltbook” functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 0
- Schema quality: 1805 → 2213 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- New tool “memory_object” functional
- New tool “memory_resolve_objection” functional
- “memory_remember” added an optional parameter “check” cosmetic
- “memory_remember” added an optional parameter “supersede_kind” cosmetic
- 19 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://genesis-verify.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of genesis-verify.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://genesis-verify.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://genesis-verify.vercel.app/api/mcp | HTTPS enforced | 308 | https://genesis-verify.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
how_to_use ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
new_since_colony ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| post_id | string | yes | – |
No output schema declared.
No examples provided.
new_since_moltbook ~39
Same seen-check on Moltbook threads (nested replies flattened).
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| post_id | string | yes | – |
No output schema declared.
No examples provided.
resolve_colony ~101
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).
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_parent | string | – | – |
| expect_len | number | – | – |
| expect_sha256 | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
resolve_moltbook ~48
Resolve a Moltbook post id (for a comment add post=<post-id>). Returns exists, author, title.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| post | string | – | – |
No output schema declared.
No examples provided.
resolve_swarmmemo ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_parent | string | – | – |
| expect_sha256 | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.MagneticSnake/genesis-memory MCP server?
io.github.MagneticSnake/genesis-memory is a hosted endpoint at https://genesis-verify.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · genesis-verify.vercel.app
claude mcp add --transport http magneticsnake-genesis-memory 'https://genesis-verify.vercel.app/api/mcp'
What is the io.github.MagneticSnake/genesis-memory MCP server?
io.github.MagneticSnake/genesis-memory is an MCP server listed in the public MCP registry as io.github.MagneticSnake/genesis-memory. Provenance-carrying memory for AI agents: corrections supersede, never overwrite. Free, API + MCP. This page covers its hosted endpoint (https://genesis-verify.vercel.app/api/mcp).
Is the io.github.MagneticSnake/genesis-memory MCP server safe to use?
io.github.MagneticSnake/genesis-memory scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.MagneticSnake/genesis-memory MCP server expose?
io.github.MagneticSnake/genesis-memory exposes 6 tools: how_to_use, resolve_colony, resolve_moltbook, resolve_swarmmemo, new_since_colony, new_since_moltbook. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.
Does the io.github.MagneticSnake/genesis-memory MCP server require authentication?
No. We connected to io.github.MagneticSnake/genesis-memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.MagneticSnake/genesis-memory MCP server still maintained?
io.github.MagneticSnake/genesis-memory is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.