io.github.emercoin/emercoin-agent

Est-ce que io.github.emercoin/emercoin-agent est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.emercoin/emercoin-agent » 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 5 outils

• node_status≈ 333 tokens

  Report the Emercoin node's version, block height, header height, peer connections and sync state (`synced` true once block == header height). Read-only, no sign-in required, no parameters. Call it first in a session to confirm the node is healthy and fully synced before trusting `read_record` or writing with `register_identity` / `store_memory`.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "node_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"blocks": "texte", "synced": "texte", "headers": "texte", "version": "texte", "connections": "texte", "verificationprogress": "texte"}}

• read_record≈ 563 tokens

  Read one Emercoin NVS (Name-Value Storage) record by its full name — an agent's identity (`ai:gh:<github_id>`) or a memory (`ai:gh:<github_id>:mem:<hash>`) written by `register_identity` / `store_memory`. Returns the confirmed on-chain record, or a `pending` one still in the mempool — the `status` field ('confirmed' | 'pending') distinguishes them. Read-only, no sign-in required; use `whoami` to find your own github_id. Returns null fields for a name that does not exist.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    Full NVS record name to read. Identity records are 'ai:gh:<github_id>' (e.g. 'ai:gh:3772563'); memory records are 'ai:gh:<github_id>:mem:<sha256-hex>'. Any existing NVS name works.

  Exemple d'appel

  {"name": "read_record", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "time": "texte", "txid": "texte", "value": "texte", "status": "texte", "address": "texte", "pending": "texte", "operation": "texte", "days_added": "texte", "pending_update": "texte", "address_is_mine": "texte"}}

• register_identity≈ 429 tokens

  Create or rotate your on-chain identity record `ai:gh:<github_id>`, binding an Emercoin address to your GitHub identity. Requires a signed-in session (OAuth) and counts against the FREE-tier per-minute write limit. Run `whoami` first to confirm you are signed in; anchor memories under this identity afterwards with `store_memory`. Writes one NVS transaction paid by the gateway (you need no EMC); the record reads back as `pending` at once and `confirmed` after the next block (~10 min on average). Idempotent — calling again rebinds the address. Returns the record name and the transaction id.

  Paramètres, retour & exemple (2)

  Paramètres

  • address · string · requis
    Emercoin address to bind to your GitHub identity, e.g. 'EVfAn...'. It is the anchor for later signature login — you must control its key (control is proven when you sign a challenge at login, not here).
  • metadata · ? · optionnel
    Optional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused.

  Exemple d'appel

  {"name": "register_identity", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "txid": "texte"}}

• store_memory≈ 385 tokens

  Anchor a memory/artifact on-chain as the NVS record `ai:gh:<github_id>:mem:<content_hash>` — a tamper-evident fingerprint others can verify later. Requires a signed-in session (OAuth) and counts against the FREE-tier per-minute write limit. Writes one NVS transaction paid by the gateway; reads back `pending` at once, `confirmed` after the next block (~10 min). Not idempotent — each distinct hash is a new record. Register your identity first. Returns the record name and the transaction id.

  Paramètres, retour & exemple (2)

  Paramètres

  • metadata · ? · optionnel
    Optional JSON object stored with the record (note, source, tags, …). Omit if unused.
  • content_hash · string · requis
    Hash of the artifact/memory, e.g. a SHA-256 hex digest. It becomes the record's ':mem:<hash>' suffix; the content itself stays off-chain (e.g. IPFS) — only this fingerprint is anchored.

  Exemple d'appel

  {"name": "store_memory", "arguments": {"content_hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "txid": "texte"}}

• whoami≈ 298 tokens

  Report the current session's identity. Read-only, no sign-in required: an anonymous session gets `{authenticated: false}` with a hint (not an error), a signed-in one gets `{authenticated: true}` plus the GitHub-rooted id, login and tariff. Call it to confirm who you are before `register_identity` / `store_memory`; an anonymous caller must sign in (GitHub OAuth) first.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "whoami", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"hint": "texte", "tariff": "texte", "github_id": "texte", "github_login": "texte", "authenticated": true}}

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://ai.emercoin.com/mcp