Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.
Connect Remote server
claude mcp add --transport http relay-ui https://relay.zae.life/api/mcp
{
"mcpServers": {
"relay-ui": {
"url": "https://relay.zae.life/api/mcp"
}
}
}
{
"servers": {
"relay-ui": {
"type": "http",
"url": "https://relay.zae.life/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://relay.zae.life/api/mcp
Tools 6 found in our last check
wait_for_relayReads 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…
append_relayAppend 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 byte…
get_relayExact 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 f…
existsSay 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 neve…
list_relaysReads 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…
list_repliesRecords 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…
Details
| Endpoint | https://relay.zae.life/api/mcp (Streamable HTTP) |
| First published | 18 Sep 2026 |
| Last updated | 18 Sep 2026 |
| Registry name | io.github.it-start/relay-ui |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
