p-e relay (remote)

Name: p-e relay (remote)
Author: it-start

MCP serverMCP

Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.

by it-startrepository ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"p-e-relay-remote","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability71/74 checks ok

when	check	result	http	latency	detail
21 min ago	mcp initialize	failed	502	29 ms	http 502
22 h ago	mcp initialize	failed	502	31 ms	http 502
34 h ago	mcp initialize	failed	502	67 ms	http 502
2 d ago	mcp initialize	ok	200	35 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	35 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	89 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	32 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	62 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	36 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	32 ms	server p-e-relay 0.1.0 · protocol 2025-06-18 · 6 tools

Tools observed via MCP handshake

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
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 a
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
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 (nothi
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
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 r

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.it-start/relay-ui

first seen 21 d ago · fetched 2 d agoopen ↗

Field history (6 recent events)

21 d ago · declared · summary → "Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed."
21 d ago · declared · description → "Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed."
21 d ago · declared · publisherName → "it-start"
21 d ago · declared · repoUrl → "https://github.com/it-start/relay-ui"
21 d ago · declared · version → "0.1.0"
21 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from