# Steledger (oci · ghcr.io/steledger/mcp:latest)

Durable identity and memory for AI agents, anchored on the Emercoin blockchain.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.steledger.com`: 65/100, [markdown](https://verifymcp.io/servers/com-steledger-gateway/api.md), [page](https://verifymcp.io/servers/com-steledger-gateway/api)
- oci · `ghcr.io/steledger/mcp:latest`: 38/100 (this document), [markdown](https://verifymcp.io/servers/com-steledger-gateway/ghcr-io-steledger-mcp-latest.md), [page](https://verifymcp.io/servers/com-steledger-gateway/ghcr-io-steledger-mcp-latest)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/steledger/mcp:latest`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 594 tokens (~66/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the Steledger MCP server?

Steledger runs locally as a container image, launched with docker run --rm -i 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.

### Claude

```bash
claude mcp add com-steledger-gateway -- docker run --rm -i ghcr.io/steledger/mcp:latest
```

### Cursor

```json
{
  "mcpServers": {
    "com-steledger-gateway": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/steledger/mcp:latest"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-steledger-gateway": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/steledger/mcp:latest"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-steledger-gateway -- docker run --rm -i ghcr.io/steledger/mcp:latest
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-steledger-gateway": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/steledger/mcp:latest"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  com-steledger-gateway:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/steledger/mcp:latest"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-steledger-gateway": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/steledger/mcp:latest"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "com-steledger-gateway": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/steledger/mcp:latest"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 38, +1)

- [functional regression] Schema quality: 59 → 66
- [functional improvement] Stability: unverified → 0.10
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 37)

First indexed and scored.

## MCP tools (9)

### `node_status` (~23 tokens)

Get Emercoin node sync status (blocks, headers, progress, synced).

### `login` (~64 tokens)

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.

### `login_poll` (~89 tokens)

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.

Input parameters:

- `session_id` (string, required)
- `wait_seconds` (integer)

### `login_with_token` (~53 tokens)

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).

Input parameters:

- `github_token` (string, required)

### `register_identity` (~58 tokens)

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.

Input parameters:

- `address` (string, required)
- `metadata`

### `store_memory` (~65 tokens)

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.

Input parameters:

- `content_hash` (string, required)
- `metadata`

### `store_memory_batch` (~96 tokens)

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).

Input parameters:

- `records` (array, required)

### `read_record` (~45 tokens)

Read any NVS record by name (e.g. ai:gh:12345 or ai:gh:12345:mem:<hash>).

Input parameters:

- `name` (string, required)

### `list_records` (~101 tokens)

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.

Input parameters:

- `github_id`
- `limit` (integer)
- `offset` (integer)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/com-steledger-gateway/ghcr-io-steledger-mcp-latest#diagnostics

## Score history

- 2026-09-25: 38
- 2026-09-24: 37
- 2026-09-23: 37
- 2026-09-22: 37

## Common questions

### 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 38 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 25 September 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.

## Links

- Repository: https://github.com/steledger/steledger-gateway
- Website: https://api.steledger.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-steledger-gateway/ghcr-io-steledger-mcp-latest.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-steledger-gateway/ghcr-io-steledger-mcp-latest.json
- HTML version of this page: https://verifymcp.io/servers/com-steledger-gateway/ghcr-io-steledger-mcp-latest