Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Authorization not required, issuer https://api.steledger.com/
Changed the definition of "transfer_records"
⟨210 unchanged words⟩ new memories are held by the gateway again. ChangingReturnsa record costs a network fee in EMC. If you hold the key and have no EMC, set `fee_grant`: the gateway then also sends 0.01 EMC (about fifty value updates) to `to_address` in a separate transaction — once per GitHub account, within a daily budget. If it is not available the call is refused before anything moves (`fee_grant_used`, `fee_grant_unavailable`), so you can decide to transfer without it. Do not ask for it with an address no one holds a key to: nobody could spend it. Returns the transaction id, the names moved, the fee funds if sent, and a plain statement of what changes.
⟨23 unchanged words⟩ ":"Everything","type":"boolean"},"fee_grant":{"default":false,"description":"Also send a small amount of EMC to `to_address` to pay network fees for changing these records later from your own node. Once per account; refused before anything moves if it is not available.","title":"Fee Grant","type":"boolean"},"irreversible":{"description":"Must be true. Confirms ⟨106 unchanged words⟩
{"$defs":{"FeeGrantResult":{"description":"Network-fee funds sent with a transfer: the amount in EMC, and the id of\nthe transaction that paid it — null if it could not be sent.","properties":{"amount":{"title":"Amount","type":"string"},"txid":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Txid"}},"required":["amount","txid"],"title":"FeeGrantResult","type":"object"},"Quota":{"description":"Writes this account has ⟨57 unchanged words⟩ ":"Count","type":"integer"},"fee_grant":{"anyOf":[{"$ref":"#/$defs/FeeGrantResult"},{"type":"null"}]},"names":{"items":{"type":"string" ⟨20 unchanged words⟩ ","count","names","to_address","after","fee_grant","quota"],"title":"TransferResult","type":"object"}
Added "send_feedback" (8 tools before, 9 now)
Send feedback — Tell 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. A person reads them over the following days; there is no automatic reply, so do not wait for one. If you are signed in, your GitHub id is kept with the message; nothing else about you is. Every refusal from this service points here.
Added "transfer_records" (7 tools before, 8 now)
Transfer records — Hand 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, and each record gets about a century added to its term, since the gateway will not be able to renew it. Why you might: with an address whose key you hold, the records are really yours — you can prove control by signing, and payments sent to your identity name reach you rather than the gateway. Changing a record afterwa…
Certificate recorded, valid to 2026-12-20
Authorization not required
Added "list_records" and "store_memory_batch"; changed the definition of "register_identity", "store_memory" and "whoami" (5 tools before, 7 now)
{"$defs":{"Quota":{"description":"Writes this account has left on its tier. `writes_open_on` (a UTC date)\nappears only while the GitHub account is too new to write.","properties":{"writes_left_this_minute":{"title":"Writes Left This Minute","type":"integer"},"writes_left_today":{"title":"Writes Left Today","type":"integer"},"writes_open_on":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Writes Open On"}},"title":"Quota","type":"object"}},"properties":{"name":{"title":"Name","type":"string"},"quota":{"$ref":"#/$defs/Quota"},"txid":{"title":"Txid","type":"string"}},"required":["name","txid","quota"],"title":"WriteResult","type":"object"}
Changed the definition of "register_identity", "store_memory" and "whoami"
⟨21 unchanged words⟩ session (OAuth) and counts against the FREE-tierper-minutewritelimit.limits (see `whoami`). Run `whoami` first to confirm you are signed ⟨171 unchanged words⟩
⟨24 unchanged words⟩ session (OAuth) and counts against the FREE-tierper-minutewritelimit.limits (see `whoami`). Writes one NVS transaction paid by the gateway;
Unknown → Live
First tool surface recorded: 5 tools (server version 1.30.0)
oci:ghcr.io/steledger/mcp:latest (package_oci) — from mcp_registry, with the record
https://api.steledger.com/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 12 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
{"$defs":{"Quota":{"description":"Writes this account has left on its tier. `writes_open_on` (a UTC date)\nappears only while the GitHub account is too new to write.","properties":{"writes_left_this_minute":{"title":"Writes Left This Minute","type":"integer"},"writes_left_today":{"title":"Writes Left Today","type":"integer"},"writes_open_on":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Writes Open On"}},"title":"Quota","type":"object"}},"properties":{"name":{"title":"Name","type":"string"},"quota":{"$ref":"#/$defs/Quota"},"txid":{"title":"Txid","type":"string"}},"required":["name","txid","quota"],"title":"WriteResult","type":"object"}
⟨128 unchanged words⟩ a GitHub account at least 30 days old. `quota` says how many writes are left right now (and, for a young account, the date writes open); every write returns the same figures, so plan batches with them. Note what this tool does not do: it ⟨35 unchanged words⟩
{"$defs":{"Quota":{"description":"Writes this account has left on its tier. `writes_open_on` (a UTC date)\nappears only while the GitHub account is too new to write.","properties":{"writes_left_this_minute":{"title":"Writes Left This Minute","type":"integer"},"writes_left_today":{"title":"Writes Left Today","type":"integer"},"writes_open_on":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Writes Open On"}},"title":"Quota","type":"object"}},"properties":{"authenticated":{"default":null,"title":"Authenticated ⟨30 unchanged words⟩ }],"default":null,"title":"Hint"},"quota":{"anyOf":[{"$ref":"#/$defs/Quota"},{"type":"null"}],"default":null},"tariff":{"anyOf":[{"type" ⟨11 unchanged words⟩
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 `expi…
Store memories (batch) — Anchor 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. All or nothing: if any item is refused (a malformed hash, say), nothing is written. Requires a signed-in session. A batch of N counts as N writes against the FREE-tier limits (10 per minute, 100 per 24 hours), so at most 10 items fit in one call on a fresh minute; the result says how many writes are left. One transac…
⟨103 unchanged words⟩ for every account today; it governs the writerate limitlimits, currently 10 writes perminute.minute and 100 per trailing 24 hours per account, and writing needs a GitHub account at least 30 days old. Note what this tool doesnot do: it reportsthe session only, reading the token your client alreadyholds without callingGitHub, and it proves nothing about control of anEmercoin address — that iswhat signing a challenge at login is for.