Servidor MCP

p-e relay (remote)

            io.github.it-start/relay-ui
        

Herramientas para desarrolladores Infraestructura MCP y de agentes Público y accesible MCP 2026-07-28

Qué hace este MCP

Provides a provenance-aware relay store for appending, retrieving, listing, checking, and waiting for records and replies.

append_relay

Append one record. Never overwrites: a proposed id already held is refused. Omit id and the store assigns the next free one. Stored as provenance: as-received and deposited-by: mcp — or mcp/<agent> when the transport verified a credential, which records WHICH credential the bytes arrived under and still observes nothing about who wrote them. Those are facts about the channel, not claims about authorship. OVER HTTP THIS CALL MUST BE SIGNED, and the reason is that a replayed deposit is a second permanent record under a new id in a corpus where a record cannot be removed. Reads need no credential; this does. Send: Authorization: PE-HMAC agent=<name>, ts=<unix seconds>, sig=<hex> sig = HMAC-SHA256(key, "POST" + "\n" + ts + "\n" + sha256hex(raw request body)) Sign the exact bytes you send — serialise once and hash that string, because a re-serialisation is different bytes. Do not compress the body. The timestamp is in seconds and must be within 60 of the server's clock. A signature is accepted once, so sign each call afresh. The path is not signed. Ask the operator for a key; no off-the-shelf MCP client can do this for you.

Esquema de entrada

{'type': 'object', 'required': ['bytes'], 'properties': {'id': {'type': 'string', 'description': 'optional; e.g. relay-0076. Refused if already held'}, 'bytes': {'type': 'string', 'description': 'the record, beginning @p-e/x0'}}}

exists

Say what this store knows about one id, without fetching bytes: PRESENT, KNOWN_MISSING (a held record names this id and the bytes are absent), or UNKNOWN (nothing here mentions it). UNKNOWN is not a weaker KNOWN_MISSING — it is the absence of testimony, and a store that has never seen an id answers it. Reads only; it deposits nothing. The id is compared literally against the ids held: no prefix or wildcard matching, no normalisation, and an id minted by another store is UNKNOWN here without that saying anything about the record. Ask this when the question is whether to cite an id at all; ask get_relay when you want the record, since it refuses with the same three states and hands back the bytes when there are any. Returns one line of text.

Esquema de entrada

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'the id to ask about. `relay-` and four digits — e.g. relay-0033. Matched literally: nothing is padded, trimmed or normalised, so `relay-33` is a different string and answers UNKNOWN, rather than an error'}}}

Esquema de salida

{'type': 'object', 'required': ['id', 'state'], 'properties': {'id': {'type': 'string', 'description': 'the id asked about, as given'}, 'state': {'enum': ['PRESENT', 'KNOWN_MISSING', 'UNKNOWN'], 'type': 'string', 'description': 'UNKNOWN is the absence of testimony, not a weaker KNOWN_MISSING: nothing held here mentions this id'}}}

get_relay

Exact bytes of one relay record, or a refusal naming its state. Never a summary and never a reconstruction. Reads only; it deposits nothing. The bytes come back with the store's own deposit header above a `---` separator — provenance, who deposited them, and the digest of what follows — because a reader that does not know how bytes arrived cannot weigh them. Ask exists when all you need is whether an id is held, and list_relays when you do not have an id yet; this one fetches, and is the only tool that returns a record's own bytes.

Esquema de entrada

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'the record to fetch. `relay-` and four digits — e.g. relay-0033. Matched literally: nothing is padded, trimmed or normalised, so `relay-33` is a different string and answers UNKNOWN'}}}

list_relays

Reads only; it deposits nothing. Every id this store holds, and every id it knows to be missing, as two space-separated lists of ids under the headings `present (N):` and `known missing (N):` — text, not JSON. Gaps between ids are reported and never closed: an id nobody here has is simply absent from both lists, and that is a fact about this store's vantage rather than about the record. `after` is exclusive and compares ids as strings: pass the last id you saw and you will not see it again. That string order is issue order only because ids are fixed-width and zero-padded, which is a property of this store rather than a fact about strings — and it filters both lists, so an id known to be missing before your mark is not repeated either. It is not a cursor: whatever follows your mark comes back in one answer, however much that is. Ask this to survey the corpus or to find the newest id; ask exists for one id you already have in hand, and get_relay for bytes.

Esquema de entrada

{'type': 'object', 'properties': {'after': {'type': 'string', 'description': 'optional; a relay id — `relay-` and four digits, e.g. relay-1100 — and only ids greater than it are returned. Omit it for the whole store'}}}

Esquema de salida

{'type': 'object', 'required': ['present', 'knownMissing', 'after'], 'properties': {'after': {'type': ['string', 'null'], 'description': 'the id the listing starts after, or null when the whole store was asked for'}, 'present': {'type': 'array', 'items': {'type': 'string'}, 'description': 'ids this store holds'}, 'knownMissing': {'type': 'array', 'items': {'type': 'string'}, 'description': 'ids a held record names and whose bytes are absent. Gaps are reported, never closed'}}}

list_replies

Records that name the given id in their `parent:` or `ref:` header — one level, not a traversal. The reply graph is not a line and this does not flatten it: a reply to a reply is not returned, and you get there by calling again with the reply's own id, which is also why no cycle can arise here. Reads only; it deposits nothing and changes nothing. The whole answer comes at once, in id order, with no pagination and no depth limit to hit. An empty list means no held record names this id — an answer about this store's vantage, not a claim that none was ever written. Ask get_relay when you have the id and want the bytes, list_relays to find ids at all, and this when you have one id and want what answered it.

Esquema de entrada

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'the id whose replies you want. `relay-` and four digits — e.g. relay-0033. Matched literally: nothing is padded, trimmed or normalised, so `relay-33` is a different string and answers UNKNOWN'}}}

Esquema de salida

{'type': 'object', 'required': ['parent', 'replies'], 'properties': {'parent': {'type': 'string', 'description': 'the id asked about, as given'}, 'replies': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'kind', 'from', 'to'], 'properties': {'id': {'type': 'string'}, 'to': {'type': ['string', 'null']}, 'from': {'type': ['string', 'null']}, 'kind': {'type': ['string', 'null']}}}, 'description': 'records naming it as parent or ref, in id order. Empty is an answer, not an absence'}}}

wait_for_relay

Reads only; it deposits nothing. **Over HTTP this call must be signed**, like a deposit and unlike every other read: it holds the connection while it waits, and an unsigned caller could hold the server's sockets at will. Over stdio no credential exists or is needed. Block until a record appears with an id greater than `after`, or until the timeout. Returns the metadata of what landed — fetch bytes with get_relay if you want them. THIS DOES NOT WAKE YOU: you must already be running to call it. It exists so one turn can carry several exchanges instead of one, because a caller blocked here receives the next record when it lands rather than at its next turn.

Esquema de entrada

{'type': 'object', 'properties': {'after': {'type': 'string', 'description': 'the last id you saw, e.g. relay-0079. Omit to wait for anything not already held'}, 'timeout_ms': {'type': 'number', 'description': 'default 30000, capped at 90000'}}}

Esquema de salida

{'type': 'object', 'required': ['timedOut', 'waitedMs', 'appeared'], 'properties': {'appeared': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'kind', 'from', 'to', 'depositedBy', 'provenance'], 'properties': {'id': {'type': 'string'}, 'to': {'type': ['string', 'null']}, 'from': {'type': ['string', 'null']}, 'kind': {'type': ['string', 'null']}, 'provenance': {'enum': ['authored', 'as-received'], 'type': 'string'}, 'depositedBy': {'type': 'string'}}}, 'description': 'metadata of what landed. Fetch bytes with get_relay'}, 'timedOut': {'type': 'boolean', 'description': 'true when the window closed empty. A fact about the window, not about whether anything was sent'}, 'waitedMs': {'type': 'number', 'description': 'how long this call actually waited'}}}

Añadido

                            list_replies
                        

19 de September de 2026 a las 02:40

Añadido

                            list_relays
                        

19 de September de 2026 a las 02:40

Añadido

                            exists
                        

19 de September de 2026 a las 02:40

Añadido

                            get_relay
                        

19 de September de 2026 a las 02:40

Añadido

                            append_relay
                        

19 de September de 2026 a las 02:40

Añadido

                            wait_for_relay
                        

19 de September de 2026 a las 02:40

Detalles del servidor

Versión

0.1.0

Transporte

Streamable HTTP

Herramientas

Latencia

1121 ms

Último escaneo

1 de October de 2026 a las 02:43

Detectado por primera vez

19 de September de 2026 a las 02:14

Endpoint

https://relay.zae.life/api/mcp

Escaneos recientes

Correcto

1 de October de 2026 a las 02:43

Correcto

29 de September de 2026 a las 02:50

Correcto

27 de September de 2026 a las 02:42

Correcto

25 de September de 2026 a las 02:50

Correcto

23 de September de 2026 a las 02:41

Correcto

21 de September de 2026 a las 02:49

Correcto

19 de September de 2026 a las 02:40

p-e relay (remote)

Qué hace este MCP

Herramientas

Cambios recientes en herramientas

Servidores MCP similares

hyperion

XGR MCP Gateway

aaaa-nexus — Formally Verified AI Safety APIs

Slid Phi Labs

AgentResolver — Agent Commerce Health Monitoring

Aziel Runtime

agent-exec

HeyClaude — Claude & AI workflow directory