MCP-Server
Steledger
com.steledger/gateway
Was dieses MCP kann
Registers agent identities and anchors memory or artifact hashes in Emercoin on-chain records, with tools for reading, listing, and transferring records.
Funktionen
Tools
9
Tools
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.
Nur Lesen
Externer Zugriff
Idempotent
Eingabeschema
{'type': 'object', 'title': 'list_recordsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 50, 'maximum': 200, 'minimum': 1, 'description': 'Records per page, 1–200.'}, 'offset': {'type': 'integer', 'title': 'Offset', 'default': 0, 'minimum': 0, 'description': 'Where the page starts; use `next_offset` from the previous page.'}, 'github_id': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Github Id', 'default': None, 'description': 'Numeric GitHub id whose records to list. Omit it to list your own (needs a signed-in session; `whoami` shows the id).'}}}
Ausgabeschema
{'type': 'object', '$defs': {'RecordEntry': {'type': 'object', 'title': 'RecordEntry', 'properties': {'kind': {'type': 'string', 'title': 'Kind'}, 'name': {'type': 'string', 'title': 'Name'}, 'address': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Address'}, 'expired': {'type': 'boolean', 'title': 'Expired'}, 'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'string'}, {'type': 'null'}], 'title': 'Metadata'}, 'expires_in': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Expires In'}, 'content_hash': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Content Hash'}, 'registered_at': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Registered At'}}, 'description': 'One record under a GitHub id. `kind` is identity, memory or other;\n`content_hash` is set for memories, `address` for the identity record.'}}, 'title': 'RecordList', 'required': ['github_id', 'total', 'offset', 'next_offset', 'records'], 'properties': {'total': {'type': 'integer', 'title': 'Total'}, 'offset': {'type': 'integer', 'title': 'Offset'}, 'records': {'type': 'array', 'items': {'$ref': '#/$defs/RecordEntry'}, 'title': 'Records'}, 'github_id': {'type': 'integer', 'title': 'Github Id'}, 'next_offset': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Next Offset'}}}
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.
Nur Lesen
Externer Zugriff
Idempotent
Eingabeschema
{'type': 'object', 'title': 'node_statusArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', 'title': 'NodeStatus', 'properties': {'blocks': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Blocks', 'default': None}, 'synced': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Synced', 'default': None}, 'headers': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Headers', 'default': None}, 'version': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Version', 'default': None}, 'connections': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Connections', 'default': None}, 'verificationprogress': {'anyOf': [{'type': 'number'}, {'type': 'null'}], 'title': 'Verificationprogress', 'default': None}}}
read_record
Read NVS record
Read 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 as well as here.
Returns the confirmed on-chain record, or a `pending` one still in the mempool —
the `status` field ('confirmed' | 'pending') distinguishes them. A name is only
held for a limited term, so check `expired` (and `expires_in`, in blocks) before
trusting a record: a lapsed name still reads back as 'confirmed' but can be
re-registered by anyone. Read-only, no sign-in required; use `whoami` to find
your own github_id. A name that has never been written is an error, not an
empty record — handle the failure, do not test the fields for null.
`name` is the full NVS name and is capped at 512 bytes by the chain.
Nur Lesen
Externer Zugriff
Idempotent
Eingabeschema
{'type': 'object', 'title': 'read_recordArguments', 'required': ['name'], 'properties': {'name': {'type': 'string', 'title': 'Name', 'description': "Full NVS record name to read. Identity records are 'ai:gh:<github_id>' (e.g. 'ai:gh:3772563'); memory records are 'ai:gh:<github_id>:mem:<sha256-hex>'. Any existing NVS name works."}}}
Ausgabeschema
{'type': 'object', 'title': 'NvsRecord', 'properties': {'name': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Name', 'default': None}, 'time': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Time', 'default': None}, 'txid': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Txid', 'default': None}, 'value': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Value', 'default': None}, 'status': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Status', 'default': None}, 'address': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Address', 'default': None}, 'expired': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Expired', 'default': None}, 'pending': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Pending', 'default': None}, 'operation': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Operation', 'default': None}, 'days_added': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Days Added', 'default': None}, 'expires_at': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Expires At', 'default': None}, 'expires_in': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Expires In', 'default': None}, 'pending_update': {'anyOf': [{'type': 'boolean'}, {'type': 'null'}], 'title': 'Pending Update', 'default': None}, 'address_is_mine': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Address Is Mine', 'default': None}}}
register_identity
Register identity
Create 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 memories under this identity afterwards with
`store_memory`. Writes one NVS transaction paid by the gateway (you need no EMC);
the record reads back as `pending` at once and `confirmed` after the next block
(about 8 minutes on average lately). Idempotent — calling again rebinds the address, and
`metadata` is replaced rather than merged.
Limits worth knowing before you call: `metadata` is stored verbatim in the
record value alongside your github id, login and address, and the whole value
must stay under 20 KiB — the chain rejects more. Every 128 bytes of name plus
value adds about 0.0001 EMC to the fee the gateway pays for you. The value is
written to a public chain exactly as given and cannot be deleted, so put
nothing private in it. `address` is not parsed or checked here — any string is
accepted, because control is proven later by signing a challenge at login, so
a typo surfaces then rather than now. Returns the record name and the
transaction id.
Externer Zugriff
Idempotent
Eingabeschema
{'type': 'object', 'title': 'register_identityArguments', 'required': ['address'], 'properties': {'address': {'type': 'string', 'title': 'Address', 'description': "Emercoin address to bind to your GitHub identity, e.g. 'EVfAn...'. It is the anchor for later signature login — you must control its key (control is proven when you sign a challenge at login, not here)."}, 'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Metadata', 'default': None, 'description': 'Optional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused.'}}}
Ausgabeschema
{'type': 'object', '$defs': {'Quota': {'type': 'object', 'title': 'Quota', 'properties': {'writes_open_on': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Writes Open On'}, 'writes_left_today': {'type': 'integer', 'title': 'Writes Left Today'}, 'writes_left_this_minute': {'type': 'integer', 'title': 'Writes Left This Minute'}}, '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.'}}, 'title': 'WriteResult', 'required': ['name', 'txid', 'quota'], 'properties': {'name': {'type': 'string', 'title': 'Name'}, 'txid': {'type': 'string', 'title': 'Txid'}, 'quota': {'$ref': '#/$defs/Quota'}}}
send_feedback
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.
Eingabeschema
{'type': 'object', 'title': 'send_feedbackArguments', 'required': ['message'], 'properties': {'tool': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Tool', 'default': None, 'description': "The tool the message is about, e.g. 'read_record'."}, 'message': {'type': 'string', 'title': 'Message', 'maxLength': 1000, 'description': 'Up to 1000 characters: what you tried, what came back, what you expected. No secrets — a person reads this.'}, 'error_code': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Error Code', 'default': None, 'description': "The `error` code you received, if this is about one, e.g. 'not_found'."}}}
Ausgabeschema
{'type': 'object', 'title': 'FeedbackReceipt', 'required': ['received', 'id', 'note'], 'properties': {'id': {'type': 'string', 'title': 'Id'}, 'note': {'type': 'string', 'title': 'Note'}, 'received': {'type': 'boolean', 'title': 'Received'}}}
store_memory
Store memory
Anchor 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, timestamped proof that
content with this hash existed, which anyone can verify later; `list_records`
finds your earlier ones again. Requires a signed-in session (OAuth) and counts against the
FREE-tier write limits (see `whoami`). Writes one NVS transaction paid by the gateway;
reads back `pending` at once, `confirmed` after the next block (about 8 minutes on average lately). Not
idempotent — each distinct hash is a new record. Register your identity first
— nothing enforces it, the write succeeds either way, but a memory under an
unregistered id anchors to nobody and proves correspondingly little.
Writing a hash you already anchored renews that record: its term is extended
(terms add up), and its metadata is replaced by what you pass now — so pass
the old metadata again if you want to keep it. That is the only renewal there
is; a record left alone lapses after its term (see `expires_in`).
Limits worth knowing before you call: `content_hash` becomes part of the
record *name*, `ai:gh:<github_id>:mem:<hash>`, so it must look like a digest:
32–128 characters of letters, digits, '_' or '-' (hex of any common algorithm,
or an IPFS CID); anything else is refused with `invalid_hash` before any quota
is spent. Beyond that shape it is never verified: nothing checks that it is
the hash of anything, so a wrong digest anchors happily and proves nothing. `metadata` goes verbatim
into the record value, which must stay under 20 KiB, is public and permanent.
Returns the record name and the transaction id.
Externer Zugriff
Eingabeschema
{'type': 'object', 'title': 'store_memoryArguments', 'required': ['content_hash'], 'properties': {'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Metadata', 'default': None, 'description': 'Optional JSON object stored with the record (note, source, tags, …). Omit if unused.'}, 'content_hash': {'type': 'string', 'title': 'Content Hash', 'description': "Hash of the artifact/memory, e.g. a SHA-256 hex digest. It becomes the record's ':mem:<hash>' suffix; the content itself stays off-chain (e.g. IPFS) — only this fingerprint is anchored."}}}
Ausgabeschema
{'type': 'object', '$defs': {'Quota': {'type': 'object', 'title': 'Quota', 'properties': {'writes_open_on': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Writes Open On'}, 'writes_left_today': {'type': 'integer', 'title': 'Writes Left Today'}, 'writes_left_this_minute': {'type': 'integer', 'title': 'Writes Left This Minute'}}, '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.'}}, 'title': 'WriteResult', 'required': ['name', 'txid', 'quota'], 'properties': {'name': {'type': 'string', 'title': 'Name'}, 'txid': {'type': 'string', 'title': 'Txid'}, 'quota': {'$ref': '#/$defs/Quota'}}}
store_memory_batch
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 transaction id comes back for the whole batch; each name reads back
`pending` at once and `confirmed` after the next block.
Externer Zugriff
Eingabeschema
{'type': 'object', '$defs': {'MemoryItem': {'type': 'object', 'title': 'MemoryItem', 'properties': {'metadata': {'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}], 'title': 'Metadata'}, 'content_hash': {'type': 'string', 'title': 'Content Hash'}}}}, 'title': 'store_memory_batchArguments', 'required': ['records'], 'properties': {'records': {'type': 'array', 'items': {'$ref': '#/$defs/MemoryItem'}, 'title': 'Records', 'maxItems': 100, 'minItems': 1, 'description': '1–100 items, each {"content_hash": "<digest>", "metadata": {...}}; metadata is optional. Same rules as store_memory for each item.'}}}
Ausgabeschema
{'type': 'object', '$defs': {'Quota': {'type': 'object', 'title': 'Quota', 'properties': {'writes_open_on': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Writes Open On'}, 'writes_left_today': {'type': 'integer', 'title': 'Writes Left Today'}, 'writes_left_this_minute': {'type': 'integer', 'title': 'Writes Left This Minute'}}, '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.'}}, 'title': 'BatchWriteResult', 'required': ['txid', 'count', 'names', 'quota'], 'properties': {'txid': {'type': 'string', 'title': 'Txid'}, 'count': {'type': 'integer', 'title': 'Count'}, 'names': {'type': 'array', 'items': {'type': 'string'}, 'title': 'Names'}, 'quota': {'$ref': '#/$defs/Quota'}}}
transfer_records
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 afterwards needs your
own Emercoin node and its fees. With an address no one holds a key to, the
records are sealed: provably unchangeable by anyone until the term ends. If you
only want proof that something existed at a given time, do not transfer — a
record held by the gateway is already dated.
Only records under your own identity (`ai:gh:<github_id>` and its `:mem:`
records) can be moved, and only once they are confirmed. Requires a signed-in
session; each record counts as one write against the FREE-tier limits. After
a transfer, register_identity and re-storing a moved hash fail with
`not_held`; new memories are held by the gateway again. Returns the
transaction id, the names moved, and a plain statement of what changes.
Destruktiv
Externer Zugriff
Eingabeschema
{'type': 'object', 'title': 'transfer_recordsArguments', 'required': ['to_address', 'irreversible'], 'properties': {'names': {'anyOf': [{'type': 'array', 'items': {'type': 'string'}, 'maxItems': 100}, {'type': 'null'}], 'title': 'Names', 'default': None, 'description': 'Records to transfer, e.g. ["ai:gh:123", "ai:gh:123:mem:<hash>"] — only your own. Omit and set `everything` instead to move them all.'}, 'everything': {'type': 'boolean', 'title': 'Everything', 'default': False, 'description': 'Transfer your identity and every live memory at once (up to 100). Use instead of `names`.'}, 'to_address': {'type': 'string', 'title': 'To Address', 'description': 'Emercoin address that will hold the records from now on. Any valid address is accepted: one whose key you hold, or one no one holds a key to, which seals the records.'}, 'irreversible': {'type': 'boolean', 'title': 'Irreversible', 'description': 'Must be true. Confirms you understand the gateway can never change, renew or return these records afterwards.'}}}
Ausgabeschema
{'type': 'object', '$defs': {'Quota': {'type': 'object', 'title': 'Quota', 'properties': {'writes_open_on': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Writes Open On'}, 'writes_left_today': {'type': 'integer', 'title': 'Writes Left Today'}, 'writes_left_this_minute': {'type': 'integer', 'title': 'Writes Left This Minute'}}, '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.'}}, 'title': 'TransferResult', 'required': ['txid', 'count', 'names', 'to_address', 'after', 'quota'], 'properties': {'txid': {'type': 'string', 'title': 'Txid'}, 'after': {'type': 'string', 'title': 'After'}, 'count': {'type': 'integer', 'title': 'Count'}, 'names': {'type': 'array', 'items': {'type': 'string'}, 'title': 'Names'}, 'quota': {'$ref': '#/$defs/Quota'}, 'to_address': {'type': 'string', 'title': 'To Address'}}}
whoami
Who am I
Report 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_identity` /
`store_memory`; an anonymous caller must sign in (GitHub OAuth) first.
`github_id` is the one field you usually need: every record name is built
from it — `ai:gh:<github_id>` and `ai:gh:<github_id>:mem:<hash>` — so this is
how you learn which names are yours to write and to read back.
`tariff` is `free` for every account today; it governs the write limits,
currently 10 writes per minute and 100 per trailing 24 hours per account, and
writing needs 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 reports the session only, reading the token your client already
holds without calling GitHub, and it proves nothing about control of an
Emercoin address — that is what signing a challenge at login is for.
Nur Lesen
Idempotent
Eingabeschema
{'type': 'object', 'title': 'whoamiArguments', 'properties': {}}
Ausgabeschema
{'type': 'object', '$defs': {'Quota': {'type': 'object', 'title': 'Quota', 'properties': {'writes_open_on': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Writes Open On'}, 'writes_left_today': {'type': 'integer', 'title': 'Writes Left Today'}, 'writes_left_this_minute': {'type': 'integer', 'title': 'Writes Left This Minute'}}, '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.'}}, 'title': 'WhoAmI', 'properties': {'hint': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Hint', 'default': None}, 'quota': {'anyOf': [{'$ref': '#/$defs/Quota'}, {'type': 'null'}], 'default': None}, 'tariff': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Tariff', 'default': None}, 'github_id': {'anyOf': [{'type': 'integer'}, {'type': 'null'}], 'title': 'Github Id', 'default': None}, 'github_login': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Github Login', 'default': None}, 'authenticated': {'type': 'boolean', 'title': 'Authenticated', 'default': None}}}
Verlauf
Letzte Tool-Änderungen
Hinzugefügt
send_feedback
1. October 2026 02:43
Hinzugefügt
transfer_records
25. September 2026 02:49
Hinzugefügt
store_memory_batch
25. September 2026 02:49
Geändert
store_memory
25. September 2026 02:49
Geändert
register_identity
25. September 2026 02:49
Geändert
whoami
25. September 2026 02:49
Hinzugefügt
list_records
25. September 2026 02:49
Geändert
read_record
25. September 2026 02:49
Geändert
node_status
25. September 2026 02:49
Hinzugefügt
store_memory
23. September 2026 02:40
Hinzugefügt
register_identity
23. September 2026 02:40
Hinzugefügt
whoami
23. September 2026 02:40
Hinzugefügt
read_record
23. September 2026 02:40
Hinzugefügt
node_status
23. September 2026 02:40
Entdecken
Ähnliche MCP-Server
Delx Commerce — Pay-per-Result APIs for Agents
io.github.davidmosiah/delx-mcp-a2a
Provides pay-per-result APIs and agent protocol tools for continuity, multi-agent coordination, document OCR, and crypto-related …
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
Provides an MCP gateway connecting SAP-related tools with Solana, DeFi, decentralized identity, and x402 payments.
TheProtocol — Sovereign AI Agent Platform
cloud.theprotocol/registry
Manages sovereign AI agents, identities, contracts, payments, governance, exchanges, and cross-frame token transfers.
AgentBIT
app.agentbit/mcp
Routes pay-per-call tools over x402 on Base, covering discovery, data conversion, company research, counterparty screening, domai…
XGR MCP Gateway
io.github.xgr-network/xdala-workflow-builder
Provides an MCP gateway for XGRChain and XDaLa workflows, including blockchain explorer queries, session inspection, transaction …
Wisely x402 Agent-Payment Infrastructure
com.wiselyenterprisesllc/x402-agent-payment-infrastructure
Provides agent payment workflows for x402 endpoints, wallet handoffs, receipts, creator catalogs, local commerce bridges, endpoin…
Taifoon coordination layer
io.taifoon/coordination-layer
Coordinates agent registration, hiring, benchmarking, resource grids, assurance workflows, and blockchain-based settlement and pr…
MolTrust MCP Server
io.github.MoltyCel/moltrust-mcp-server
Provides agent identity, trust scoring, verifiable credentials, reputation, Sybil analysis, and on-chain mandate verification.