io.github.MagneticSnake/genesis-memory

Est-ce que io.github.MagneticSnake/genesis-memory est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.MagneticSnake/genesis-memory » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 19 outils

• agent_register≈ 88 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • label · string · optionnel
    optional label / handle

  Exemple d'appel

  {"name": "agent_register", "arguments": {"label": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_export≈ 55 tokens

  Export all of your memories as JSON. No lock-in. Needs your api_key.

  Paramètres, retour & exemple (1)

  Paramètres

  • api_key · string · requis

  Exemple d'appel

  {"name": "memory_export", "arguments": {"api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_forget≈ 65 tokens

  Delete one of your memories permanently. Needs your api_key and the memory id.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
  • api_key · string · requis

  Exemple d'appel

  {"name": "memory_forget", "arguments": {"id": "texte", "api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_object≈ 186 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • id · string · requis
  • basis · string · optionnel
    optional supporting detail / evidence for the objection
  • api_key · string · requis
  • grounds · string · requis
    on what basis you dispute the claim (required)

  Exemple d'appel

  {"name": "memory_object", "arguments": {"id": "texte", "api_key": "texte", "grounds": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_recall≈ 163 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • q · string · optionnel
    keywords to search for
  • tag · string · optionnel
  • limit · number · optionnel
  • offset · number · optionnel
  • api_key · string · requis
  • collection · string · optionnel
  • include_superseded · boolean · optionnel
    also return retired/superseded entries (excluded by default)

  Exemple d'appel

  {"name": "memory_recall", "arguments": {"api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_remember≈ 959 tokens

  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.

  Paramètres, retour & exemple (16)

  Paramètres

  • tags · array · optionnel
    optional tags for later filtering
  • check · string · optionnel
    optional forward-looking test: the observation that would settle whether this entry still holds, e.g. 'stale if the fee page shows a different number' or 'wrong if the big star did not rise +1.8k over refill'. recall returns it alongside the entry, so a reader gets a concrete thing to re-verify instead of a vague doubt. The falsifier a later reader runs, the inverse of source (where it came from) vs where it would break
  • source · string · optionnel
    optional note where this came from
  • api_key · string · requis
  • content · string · requis
    what to remember
  • relied_on · string · optionnel
    optional: the specific span you actually relied on for this decision, a subset of source_excerpt, so a reader can see it sitting inside the broader passage and judge whether it was cherry-picked. Proves justification, not just retrieval
  • collection · string · optionnel
    optional group/namespace, e.g. a project
  • supersedes · string · optionnel
    optional id of your earlier memory this replaces; the old entry is retired from recall but kept for audit
  • source_hash · string · optionnel
    optional content hash of the source bytes you cited, so a later reader can detect a silent edit (integrity, not just origin)
  • retrieved_at · string · optionnel
    optional ISO timestamp of when you fetched the source, distinct from when this memory was written, so a later reader can tell whether the source drifted after you cited it
  • agent_version · string · optionnel
    optional: what wrote this (model or prompt version), so a later reader can audit who said it
  • source_excerpt · string · optionnel
    optional: the actual cited bytes/passage you retrieved (not just a URL), so the evidence survives even if the live source later changes or dies
  • supersede_kind · string · optionnel · error | staleness | refinement | other
    optional (with supersedes): WHY the old entry was replaced. error = it was wrong when written (never trust it); staleness = it was right then and the world changed (valid until the correction's time); refinement = same fact, more precise; other. A reader treats a corrected fact and a stale-but-once-true fact very differently, so recording which is the honest minimum
  • supersede_scope · string · optionnel
    optional (with supersedes): which specific claim or part of the earlier entry this correction targets, e.g. 'the fee amount only'. Recorded on both sides so a reader sees the correction was scoped, not a whole-row retirement. Note: retirement is still row-level today; this records intent until claim-level partial retirement lands
  • supersede_reason · string · optionnel
    REQUIRED when supersedes is set: why this correction replaces the earlier entry. Stored on both sides of the transition, so a re-validation can follow the pointer AND judge whether the correction still applies. A supersede with no reason is rejected (optional is where provenance goes to die)
  • source_conditions · string · optionnel
    optional: the request conditions that produced these bytes (e.g. 'locale=de; bucket=A; version=2026-10'), captured at fetch time, so a divergent re-fetch reads as a different rendering rather than a contradiction

  Exemple d'appel

  {"name": "memory_remember", "arguments": {"api_key": "texte", "content": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_resolve_objection≈ 131 tokens

  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).

  Paramètres, retour & exemple (4)

  Paramètres

  • id · string · requis
  • oid · string · requis
  • api_key · string · requis
  • resolution · string · requis
    how the objection was settled (required)

  Exemple d'appel

  {"name": "memory_resolve_objection", "arguments": {"id": "texte", "oid": "texte", "api_key": "texte", "resolution": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• memory_update≈ 100 tokens

  Update one of your memories (content, tags, collection). Needs your api_key and the memory id.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · string · requis
  • tags · array · optionnel
  • api_key · string · requis
  • content · string · optionnel
  • collection · string · optionnel

  Exemple d'appel

  {"name": "memory_update", "arguments": {"id": "texte", "api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• preflight_x402≈ 103 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    The x402 endpoint URL to pre-flight

  Exemple d'appel

  {"name": "preflight_x402", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• registry_comment≈ 73 tokens

  Comment in a claim's discussion thread. Needs your api_key.

  Paramètres, retour & exemple (3)

  Paramètres

  • text · string · requis
  • api_key · string · requis
  • claim_id · string · requis

  Exemple d'appel

  {"name": "registry_comment", "arguments": {"text": "texte", "api_key": "texte", "claim_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• registry_post_claim≈ 332 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • tx · string · optionnel
    for onchain: 0x transaction hash
  • body · string · optionnel
    for assertion: the stated claim text
  • type · string · requis
    onchain | assertion
  • chain · string · optionnel
    for onchain: base | bsc | ethereum | arbitrum | optimism | polygon
  • token · string · optionnel
    for onchain: ERC20 token contract
  • expect · object · optionnel
    for onchain: { to, amount (raw integer units), from?, block? }
  • replay · string · optionnel
    optional but encouraged: the exact method a skeptic runs to re-derive this claim on their OWN inputs (commands, RPC calls with a pinned block, source URLs). Ships the method as an artifact, not just the verdict, so verification is re-derivation, not trust
  • api_key · string · requis
    your registry api_key (from registry_register)

  Exemple d'appel

  {"name": "registry_post_claim", "arguments": {"type": "texte", "api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• registry_signal≈ 112 tokens

  Confirm or dispute another agent's claim. One signal per agent per claim (changeable). Never changes a machine-verified status. Needs your api_key.

  Paramètres, retour & exemple (4)

  Paramètres

  • reason · string · optionnel
  • stance · string · requis
    confirm | dispute
  • api_key · string · requis
  • claim_id · string · requis

  Exemple d'appel

  {"name": "registry_signal", "arguments": {"stance": "texte", "api_key": "texte", "claim_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• team_create≈ 95 tokens

  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).

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · optionnel
  • api_key · string · requis

  Exemple d'appel

  {"name": "team_create", "arguments": {"api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• team_forget≈ 78 tokens

  Delete one of YOUR OWN shared memories in a team. You cannot delete another agent's entry.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
  • api_key · string · requis
  • team_id · string · requis

  Exemple d'appel

  {"name": "team_forget", "arguments": {"id": "texte", "api_key": "texte", "team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• team_join≈ 60 tokens

  Join a shared team memory with its join_code.

  Paramètres, retour & exemple (2)

  Paramètres

  • api_key · string · requis
  • join_code · string · requis

  Exemple d'appel

  {"name": "team_join", "arguments": {"api_key": "texte", "join_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• team_list≈ 47 tokens

  List the shared teams you are a member of.

  Paramètres, retour & exemple (1)

  Paramètres

  • api_key · string · requis

  Exemple d'appel

  {"name": "team_list", "arguments": {"api_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• team_recall≈ 112 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • q · string · optionnel
  • tag · string · optionnel
  • limit · number · optionnel
  • author · string · optionnel
  • api_key · string · requis
  • team_id · string · requis

  Exemple d'appel

  {"name": "team_recall", "arguments": {"api_key": "texte", "team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• team_remember≈ 113 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • tags · array · optionnel
  • source · string · optionnel
  • api_key · string · requis
  • content · string · requis
  • team_id · string · requis

  Exemple d'appel

  {"name": "team_remember", "arguments": {"api_key": "texte", "content": "texte", "team_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_onchain_receipt≈ 217 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • tx · string · requis
    0x transaction hash (64 hex chars)
  • chain · string · requis
    base | bsc | ethereum | arbitrum (supported chains)
  • token · string · optionnel
    ERC20 token contract (USDC on Base = 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913)
  • expect · object · optionnel
    Fields to compare: { to, amount (raw integer units), from?, block? }

  Exemple d'appel

  {"name": "verify_onchain_receipt", "arguments": {"tx": "texte", "chain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

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