Server data from the Official MCP Registry
On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS).
On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS).
Remote endpoints: streamable-http: https://ai.emercoin.com/mcp
Valid MCP server (2 strong, 6 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Imported from the Official MCP Registry.
5 tools verified · Open access · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: GATEWAY_URL
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-emercoin-emercoin-agent": {
"env": {
"GATEWAY_URL": "your-gateway-url-here"
},
"url": "https://ai.emercoin.com/mcp"
}
}
}From the project's GitHub README.
emer-ai-tools)A runnable Docker stack: an Emercoin node plus an agent gateway that turns
the chain's Name-Value Storage (NVS) into an on-chain identity & memory layer for
AI agents. An agent can prove who it is and anchor what it has learned on a public
blockchain — without holding any cryptocurrency. Hosted at
ai.emercoin.com; exposed to agents as the
emercoin-agent MCP server.
🤖 Building with an AI agent? Read AGENTS.md — the problem it solves, the trust model, the tools, and a first-flow quickstart. A ready-to-use Claude Code skill ships at
.claude/skills/emercoin-identity/(invoke with/emercoin-identity). Design notes: docs/ARCHITECTURE.md.
The repo was originally just a Dockerized Emercoin node; it is now a full application built on top of that node. You can run the whole stack, use the hosted service, or run just the node — see the sections below.
AI agent ──MCP tools──▶ edge (auth boundary) ──HTTP──▶ adapter ──JSON-RPC──▶ node
│ (RPC↔REST) (NVS on-chain)
└── Redis (rate limit + login nonces)
| Component | Path | Role |
|---|---|---|
node (emc) | node/ | Emercoin core — holds the chain + hot-wallet; internal-only, authorizes nothing. |
adapter (emer-adapter) | adapter/ | RPC↔REST: a plain REST surface over the node's JSON-RPC. Internal, gated by X-Internal-Key. |
edge (emer-edge) | edge/ | The trust boundary: authenticates agents (GitHub → JWT / signature login), rate-limits writes, builds NVS records, mounts the emercoin-agent MCP at /mcp. |
| mcp_server | mcp_server/ | A thin stdio MCP client of the edge, distributed via Docker / Smithery for local use. |
| site | site/ | The public ai.emercoin.com front-end (landing, login, stats). |
The emercoin-agent MCP server is live — no self-hosting needed:
https://ai.emercoin.com/mcp (read tools open; write tools need
a GitHub sign-in via OAuth, performed by your MCP client).mcp_server/README.md.Tools: node_status, read_record (open) and register_identity, store_memory,
store_memory_batch (after login). Full reference + first-flow in AGENTS.md.
Node (mainnet) + adapter + edge + redis, dev profile:
git clone https://github.com/emercoin/emer-ai-tools && cd emer-ai-tools
cp node/emercoin.conf.example node/emercoin.conf # set rpcpassword
docker compose -f deploy/docker-compose.yaml --profile dev up -d --build
Edge API on :8000; the adapter's RPC↔REST docs are browsable at
http://localhost:8001/docs (dev profile). Wire the MCP server into your agent and
run the first flow — see the AGENTS.md quickstart.
(Use --profile prod to gate the adapter behind a shared X-Internal-Key.)
The node alone (no agent tools) is the default stack — no profile needed. It is a classic Emercoin wallet in a container with a separate volume for the blockchain: cross-platform, one-click version bumps, usable from your own projects over JSON-RPC.
cp node/emercoin.conf.example node/emercoin.conf
docker compose -f deploy/docker-compose.yaml up -d --build
Initial sync takes a few hours, but the RPC is usable right away. By default port 6662 connects to the container:
{"method": "getinfo"}Change the RPC password:
docker compose -f deploy/docker-compose.yaml exec emc bash changepass.sh
docker compose -f deploy/docker-compose.yaml restart emc
Health check — POST to http://emcrpc:emcpass@127.0.0.1:6662 with {"method":"getinfo"}:
curl --location --request POST 'emcrpc:emcpass@127.0.0.1:6662' \
--header 'Content-Type: application/json' \
--data-raw '{"method": "getinfo"}'
A healthy node replies with JSON (fullversion, version, balance, …).
Manage the build:
docker compose -f deploy/docker-compose.yaml stop emc # stop
docker compose -f deploy/docker-compose.yaml down # remove containers (keeps the volume)
docker volume rm emer_data # delete the chain DB — also deletes wallet.dat!
MVP, verified end-to-end on mainnet: identity registration, signature login, single
prod compose profile already gates the adapter behind X-Internal-Key. Details
in AGENTS.md and docs/ARCHITECTURE.md.MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.