Steledger
OCI · GHCR.IO/STELEDGER/MCP:LATEST · 2 COMPONENTS
Durable identity and memory for AI agents, anchored on the Emercoin blockchain.
Available components
Last scanned (21 hours ago)
Scores higher than 76% of OCI servers
Category Memory and Knowledge
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 & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 27 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 594 tokens (~66/item across 9 items; 9 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 −2
- Stability: pass → 0.83 functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 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 21 Nov 2026 · Analysed oci/ghcr.io/steledger/mcp:latest
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 →
list_records ~101
List every record under a GitHub id — its identity record and all its memories, newest first, with each memory's hash and metadata. This is how a new session finds what it anchored before. Omit github_id to list your own (needs login). Pass `next_offset` back as `offset` for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| github_id | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
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 ~96
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 free-tier write limits (10 per minute, 100 per trailing 24 hours per account).
| Name | Type | Req | Description |
|---|---|---|---|
| records | array | yes | – |
No output schema declared.
No examples provided.
How do I install the Steledger MCP server?
Steledger runs locally as a container image, launched with docker run --rm -i -e GATEWAY_URL ghcr.io/steledger/mcp:latest. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/steledger/mcp:latest
claude mcp add com-steledger-gateway -- docker run --rm -i -e GATEWAY_URL ghcr.io/steledger/mcp:latest
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 Steledger MCP server?
Steledger is an MCP server listed in the public MCP registry as com.steledger/gateway. Durable identity and memory for AI agents, anchored on the Emercoin blockchain. This page covers its container image (ghcr.io/steledger/mcp:latest).
Is the Steledger MCP server safe to use?
Steledger scores 51 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 Steledger MCP server expose?
Steledger exposes 9 tools: node_status, login, login_poll, login_with_token, register_identity, and 4 more. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.
Is the Steledger MCP server still maintained?
Steledger is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Steledger MCP server under?
Steledger declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Steledger MCP server?
VerifyMCP ran 12 checks on Steledger, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Steledger: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.