Steledger
v0.3.0Durable identity and memory for AI agents, anchored on the Emercoin blockchain.
Endpoint health
online- Last checked
- 11/20/2026, 8:16:34 AM
- Latency
- 337 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.steledger%2Fgateway
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.steledger/gateway": {
"url": "https://api.steledger.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
9 shown · authentication unknown
List records
list_records
List 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 the full name, hash included, and this is where the hashes come from. Read-only, no sign-in needed to list any id; omit `github_id` to list your own when signed in. What comes back is the chain's view: confirmed records only (a write still in the mempool shows up after its block), expired ones included and flagged `expired` — their names can be taken by someone else, so do not treat them as yours. Only fingerprints and metadata live here; the content itself stays wherever you stored it. Results are cached for about a minute, so a record confirmed seconds ago may take that long to appear.
Schema valid · SHA-256 529e7a15c4f6…
View input schema
{ "type": "object", "properties": { "github_id": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "default": null, "description": "Numeric GitHub id whose records to list. Omit it to list your own (needs a signed-in session; `whoami` shows the id).", "title": "Github Id" }, "limit": { "default": 50, "description": "Records per page, 1–200.", "maximum": 200, "minimum": 1, "title": "Limit", "type": "integer" }, "offset": { "default": 0, "description": "Where the page starts; use `next_offset` from the previous page.", "minimum": 0, "title": "Offset", "type": "integer" } }, "title": "list_recordsArguments" }Node status
node_status
Check 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 true once the node's verification progress passes 0.9999, so it can still be false while `blocks` and `headers` already match. Trust that field, not the arithmetic. While it is false, a `read_record` may reflect an older state of the chain; writes still work, they simply confirm later. Also the way to make sense of expiry: `expires_in` on a record is denominated in blocks, and this tool reports the current height, so the two together are the only authoritative answer to when something lapses. A term is bought in days and charged at a flat 175 blocks each; the chain has been producing about 171 a day lately (8.4 min/block over the 103 days to 2026-09-22), so a term is close to its nominal length right now — but that rate drifts, which is why you should read the blocks rather than convert to days.
Connections
streamable-http
https://api.steledger.com/mcp