
Steledger MCP server
Which servers in the official MCP registry are Steledger's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry namecom.steledger/gatewayverified in the MCP registry
The registry name sits under steledger.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools9
- Server calls itselfsteledger
- Server version0.3.0
- Protocol version2025-06-18
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 220 ms.
- Its tools do every use case we checked: anchor an agent's memory hashes on a public ledger; bind an agent's identity to its GitHub account.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- For "bind an agent's identity to its GitHub account", the likely first call is register_identity.
- Keep approval on for send_feedback: they delete, send or pay without saying so.
- transfer_records, send_feedback change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it2 of 2 use cases
- Use1 GitHub stars
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer509 ms
- Space in an agent's context≈ 3,868 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · anchor an agent's memory hashes on a public ledger
- not sure · prove to an auditor what an agent decided
- can do · bind an agent's identity to its GitHub account
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that delete, send or pay without telling the client so: send_feedback
- Tools that change data, on a server that answers without a sign-in: transfer_records, send_feedback
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
node_statusCheck that the chain node behind this service is healthy and fully synced: its version, block height, header height, peer connections and sync state. It is an Emercoin node. Read-only, no sign-in required, no parameters. `synced` is not a…
read_recordRead one on-chain 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`. Records live in Emercoin's Name-Value Storage, so anyone…
list_recordsList every record under one GitHub id — its identity record `ai:gh:<id>` and all its memories `ai:gh:<id>:mem:<hash>` — newest first, with each memory's content hash and metadata. This is how an agent starting a fresh session finds what…
whoamiReport 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…
register_identityCreate 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 write limits (see `whoami`). Run `whoami` first…
store_memoryAnchor a fingerprint of a memory or artifact on-chain as the NVS record `ai:gh:<github_id>:mem:<content_hash>`. Only the hash and your metadata are stored — never the content, which you keep wherever you like (a file, a database, IPFS)…
store_memory_batchAnchor many fingerprints in ONE on-chain transaction — the way to record a session's worth of artifacts without spending a write per minute on each. Each item becomes `ai:gh:<github_id>:mem:<content_hash>`, exactly as with `store_memory`…
transfer_recordsHand your records over from the gateway's wallet to an address you choose, in one transaction. IRREVERSIBLE: once the block confirms, the gateway can no longer change, renew or return them — nor can anyone else but the holder of…
send_feedbackTell the people running this service that something went wrong or is unclear — an error you cannot explain, a result that looks wrong, documentation that misled you, a tool you needed and did not find. Open to everyone; no sign-in. Up to…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"gateway": {
"type": "http",
"url": "https://api.steledger.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http steledger https://api.steledger.com/mcpclaude.ai, ChatGPT and other clients: add https://api.steledger.com/mcp as a custom connector in the settings.
Also shipped through: oci
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.