Emercoin Agent (moved)
OCI · DOCKER.IO/EMERCOIN/MCP:0.1.0 · 2 COMPONENTS
Moved to com.steledger/gateway — same service, now hosted at api.steledger.com.
Available components
Last scanned (22 hours ago)
Scores higher than 74% of OCI servers
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Moved: use com.steledger/gateway, same service at api.steledger.com.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 144 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 477 tokens (~59/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/docker.io/emercoin/mcp:0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
login ~64
Begin GitHub login (device flow). Returns a short code; SHOW IT TO THE USER and ask them to open `verification_uri` and enter `user_code`, then call `login_poll(session_id)` to finish. No GitHub token needed from the user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login_poll ~89
Finish device-flow login once the user has authorized. Polls for up to `wait_seconds`, caching the session JWT on success. Returns {status: "authorized", github_id, github_login} or {status: "pending"} — if pending, the user hasn't authorized yet; call this again.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
login_with_token ~53
Dev/CI fallback: log in with a pre-issued GitHub token (works only if the gateway has raw-token login enabled). Prefer `login()` (device flow).
| Name | Type | Req | Description |
|---|---|---|---|
| github_token | string | yes | – |
No output schema declared.
No examples provided.
node_status ~23
Get Emercoin node sync status (blocks, headers, progress, synced).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_record ~45
Read any NVS record by name (e.g. ai:gh:12345 or ai:gh:12345:mem:<hash>).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
register_identity ~58
Register/refresh this agent's on-chain identity record (ai:gh:<github_id>). `address` is the agent's Emercoin address, later used for signature login.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| metadata | – | – | – |
No output schema declared.
No examples provided.
store_memory ~65
Store a research/memory hash on-chain (ai:gh:<github_id>:mem:<hash>). Keep the body off-chain (e.g. IPFS); only its hash + metadata go on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | string | yes | – |
| metadata | – | – | – |
No output schema declared.
No examples provided.
store_memory_batch ~80
Store many memory hashes in ONE atomic on-chain transaction (cheaper and atomic vs. calling store_memory repeatedly). Each record is {"content_hash": str, "metadata"?: dict}. Returns one txid for the whole batch. Counts as len(records) against the per-minute write tier.
| Name | Type | Req | Description |
|---|---|---|---|
| records | array | yes | – |
No output schema declared.
No examples provided.
How do I install the Emercoin Agent (moved) MCP server?
Emercoin Agent (moved) runs locally as a container image, launched with docker run --rm -i -e GATEWAY_URL docker.io/emercoin/mcp:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/emercoin/mcp:0.1.0
claude mcp add emercoin-emercoin-agent -- docker run --rm -i -e GATEWAY_URL docker.io/emercoin/mcp:0.1.0
This image reads GATEWAY_URL. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the Emercoin Agent (moved) MCP server?
Emercoin Agent (moved) is an MCP server listed in the public MCP registry as io.github.emercoin/emercoin-agent. Moved to com.steledger/gateway, same service, now hosted at api.steledger.com. This page covers its container image (docker.io/emercoin/mcp:0.1.0).
Is the Emercoin Agent (moved) MCP server safe to use?
Emercoin Agent (moved) scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Emercoin Agent (moved) MCP server expose?
Emercoin Agent (moved) exposes 8 tools: node_status, login, login_poll, login_with_token, register_identity, and 3 more. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.
Is the Emercoin Agent (moved) MCP server still maintained?
Emercoin Agent (moved) is marked deprecated in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.