Durable identity and memory for AI agents, anchored on the Emercoin blockchain.
Connect Remote server
claude mcp add --transport http gateway https://api.steledger.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"gateway": {
"url": "https://api.steledger.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"gateway": {
"type": "http",
"url": "https://api.steledger.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.steledger.com/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 9 found in our last check
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 comparison of the two heights — it is tr…
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 can verify one in a public block explorer…
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 it anchored before: `read_record` needs th…
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 tariff. Call it to confirm who you are before `…
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 to confirm you are signed in; anchor mem…
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). What you get is a tamper-evident, timestam…
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`: only hashes and metadata, never content.…
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 `to_address`. Values are carried over unchanged, a…
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 1000 characters, a few messages per day.…
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Bearer <session JWT> from https://api.steledger.com/login — required for write tools; read tools are open |
Details
| Endpoint | https://api.steledger.com/mcp (Streamable HTTP) |
| Package | ghcr.io/steledger/mcp:latest (OCI, stdio) |
| First published | 22 Sep 2026 |
| Last updated | 22 Sep 2026 |
| Registry name | com.steledger/gateway |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
