mcpbeat

Emercoin Agent MCP Server

io.github.emercoin/emercoin-agent
answering

Emercoin Agent is answering right now. Last checked 5 min ago. It exposes 5 tools. Last commit 16 Jun 2026.

On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS).

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
205 ms
Response time
average over 24h
7
Stars
last commit 16 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add emercoin-agent --transport http https://ai.emercoin.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "emercoin-agent": {
      "url": "https://ai.emercoin.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.emercoin-agent]
url = "https://ai.emercoin.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "emercoin-agent": {
      "url": "https://ai.emercoin.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "emercoin-agent": {
      "url": "https://ai.emercoin.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

node
node_status
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`.
record
read_record
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.
register
register_identity
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.
store
store_memory
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.
whoami
whoami
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.

Endpoints

URLTransportStateLatencyChecked
https://ai.emercoin.com/mcp streamable-http answering 236 ms 5 min ago

Emercoin Agent — questions

Answers built from our own checks of this server.

What can Emercoin Agent do?
It exposes 5 tools, read directly from the server on our last check. Among them: node_status, read_record, register_identity, store_memory, whoami. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Emercoin Agent working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 205 ms. The bar chart above shows every period we have measured.
How do I connect Emercoin Agent?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Emercoin Agent need an API key?
No. Emercoin Agent completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Emercoin Agent?
It answers our handshake in 205 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Emercoin Agent open source?
Yes — it is published under the MIT licence, written in Python and 7 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.