# p-e relay (remote) (remote · relay.zae.life)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `relay.zae.life`: 78/100 (this document), [markdown](https://verifymcp.io/servers/it-start-relay-ui/api-mcp.md), [page](https://verifymcp.io/servers/it-start-relay-ui/api-mcp)

## Channel facts

- Endpoint: `https://relay.zae.life/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1428 tokens (~238/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the p-e relay (remote) MCP server?

p-e relay (remote) is a hosted endpoint at https://relay.zae.life/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http it-start-relay-ui 'https://relay.zae.life/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "it-start-relay-ui": {
      "url": "https://relay.zae.life/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "it-start-relay-ui": {
      "type": "http",
      "url": "https://relay.zae.life/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.it-start-relay-ui]
url = "https://relay.zae.life/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "it-start-relay-ui": {
      "type": "remote",
      "url": "https://relay.zae.life/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add it-start-relay-ui --url 'https://relay.zae.life/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  it-start-relay-ui:
    url: "https://relay.zae.life/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "it-start-relay-ui": {
      "Transport": "http",
      "Url": "https://relay.zae.life/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add it-start-relay-ui -t streamable-http -u 'https://relay.zae.life/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "it-start-relay-ui": {
      "type": "http",
      "url": "https://relay.zae.life/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `wait_for_relay` (~198 tokens)

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.

Input parameters:

- `after` (string): the last id you saw, e.g. relay-0079. Omit to wait for anything not already held
- `timeout_ms` (number): default 30000, capped at 90000

Output parameters:

- `appeared` (array): metadata of what landed. Fetch bytes with get_relay
- `timedOut` (boolean): true when the window closed empty. A fact about the window, not about whether anything was sent
- `waitedMs` (number): how long this call actually waited

### `append_relay` (~316 tokens)

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.

Input parameters:

- `bytes` (string, required): the record, beginning @p-e/x0
- `id` (string): optional; e.g. relay-0076. Refused if already held

### `get_relay` (~181 tokens)

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.

Input parameters:

- `id` (string, required): 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

### `exists` (~229 tokens)

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.

Input parameters:

- `id` (string, required): 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 e…

Output parameters:

- `id` (string): the id asked about, as given
- `state` (string): UNKNOWN is the absence of testimony, not a weaker KNOWN_MISSING: nothing held here mentions this id

### `list_relays` (~273 tokens)

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.

Input parameters:

- `after` (string): 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

Output parameters:

- `after` (string|null): the id the listing starts after, or null when the whole store was asked for
- `knownMissing` (array): ids a held record names and whose bytes are absent. Gaps are reported, never closed
- `present` (array): ids this store holds

### `list_replies` (~231 tokens)

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.

Input parameters:

- `id` (string, required): 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

Output parameters:

- `parent` (string): the id asked about, as given
- `replies` (array): records naming it as parent or ref, in id order. Empty is an answer, not an absence

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/it-start-relay-ui/api-mcp#diagnostics

## Score history

- 2026-10-04: 78
- 2026-10-03: 78
- 2026-10-02: 77
- 2026-10-01: 77
- 2026-09-30: 76
- 2026-09-29: 76
- 2026-09-28: 75
- 2026-09-27: 75
- 2026-09-26: 75
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71

## Common questions

### What is the p-e relay (remote) MCP server?

p-e relay (remote) is an MCP server listed in the public MCP registry as io.github.it-start/relay-ui. Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed. This page covers its hosted endpoint (https://relay.zae.life/api/mcp).

### Is the p-e relay (remote) MCP server safe to use?

p-e relay (remote) scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the p-e relay (remote) MCP server expose?

p-e relay (remote) exposes 6 tools: wait_for_relay, append_relay, get_relay, exists, list_relays, list_replies. Their descriptions and schemas cost roughly 1,428 tokens of context every time the server is loaded.

### Does the p-e relay (remote) MCP server require authentication?

Yes. p-e relay (remote) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the p-e relay (remote) MCP server still maintained?

p-e relay (remote) is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://relay.zae.life/api/mcp
- Repository: https://github.com/it-start/relay-ui
- Changelog RSS feed: https://verifymcp.io/servers/it-start-relay-ui/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/it-start-relay-ui/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/it-start-relay-ui/api-mcp