io.github.emercoin/emercoin-agent MCP Server

The io.github.emercoin/emercoin-agent MCP server provides a thin MCP client over the Emercoin edge gateway HTTP API. It enables an AI agent to use the Emercoin blockchain (NVS) as an on-chain identity and durable memory layer for agent operations.

🛠️ Key Features

On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS)
Thin MCP client over the edge gateway HTTP API
Integrates with an agent-facing IAM layer (“edge”) that delegates chain ops to a node adapter

🚀 Use Cases

Providing identity and memory for AI agents using the Emercoin blockchain (NVS)
Verifying node status via GET /status
GitHub device-flow login to support authenticated requests

⚡ Developer Benefits

Exposes 5 tools via MCP
Includes unauthenticated tool access for node_status() and login()
Implements login_poll(session_id) for device-flow completion

⚠️ Limitations

Tools described are tied to the edge gateway HTTP API (/status, /auth/github/device/start)
Auth behavior indicated as “no” for node_status() and login() based on available data

{ "type": "object", "properties": { "name": { "description": "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.", "title": "Name", "type": "string" } }, "required": [ "name" ], "title": "read_recordArguments" }

{ "type": "object", "properties": { "address": { "description": "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).", "title": "Address", "type": "string" }, "metadata": { "anyOf": [ { "additionalProperties": true, "type": "object" }, { "type": "null" } ], "default": null, "description": "Optional JSON object stored verbatim in the identity record, e.g. {\"agent\": \"my-bot\", \"url\": \"https://...\"}. Omit if unused.", "title": "Metadata" } }, "required": [ "address" ], "title": "register_identityArguments" }

{ "type": "object", "properties": { "content_hash": { "description": "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.", "title": "Content Hash", "type": "string" }, "metadata": { "anyOf": [ { "additionalProperties": true, "type": "object" }, { "type": "null" } ], "default": null, "description": "Optional JSON object stored with the record (note, source, tags, …). Omit if unused.", "title": "Metadata" } }, "required": [ "content_hash" ], "title": "store_memoryArguments" }

Tools

Tool

Auth

Maps to

node_status()

GET /status

login()

POST /auth/github/device/start (device flow; show code to user)

login_poll(session_id)

POST /auth/github/device/poll (finish; caches JWT)

login_with_token(github_token)

POST /auth/login (dev/CI fallback)

register_identity(address, metadata?)

yes

POST /nvs/identity

store_memory(content_hash, metadata?)

yes

POST /nvs/mem

store_memory_batch(records)

yes

POST /nvs/mem/batch (atomic, one tx)

read_record(name)

GET /nvs/{name}

Run (stdio transport)

bash

pip install -r requirements.txt
GATEWAY_URL=http://localhost:8000 python server.py

Claude Code MCP config example

json

{
  "mcpServers": {
    "emercoin-agent": {
      "command": "python",
      "args": ["/path/to/mcp_server/server.py"],
      "env": { "GATEWAY_URL": "http://localhost:8000" }
    }
  }
}

Emercoin Agent (moved)

io.github.emercoin/emercoin-agent MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

node_status

read_record

whoami

register_identity

store_memory

Emercoin Agent — MCP server

Tools

Config (env)

Run (stdio transport)

Claude Code MCP config example

Install

Related servers

address	string	required	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	any	optional	Optional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused.

content_hash	string	required	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.
metadata	any	optional	Optional JSON object stored with the record (note, source, tags, …). Omit if unused.