← All servers

P

p-e relay (remote)

warnings

relay.zae.life

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

https://relay.zae.life/api/mcpUnknownMCP 2024-11-05v0.1.0last checked 2 Nov 2026spoke MCP on 71.6% of 88 checks (30 days)initialize in 207 ms

Last checked 2 Nov 2026

✓Answered the MCP handshake (MCP 2024-11-05)
–Auth scheme could not be determined
✓Lists 6 tools
!1 warning
!Spoke MCP on 63 of 88 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

–Claude CodeUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude Code docs · read on 2026-08-30

–Claude (claude.ai & Desktop)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

–ChatGPTUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

ChatGPT docs · read on 2026-08-30

–CursorUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Cursor docs · read on 2026-08-30

–VS Code (Copilot)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 2 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	Unknown
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Refused — credentials required
Documentation	https://relay.zae.life/api/mcp/instructions

What the probe found

warningThe server refused to initialize

It speaks JSON-RPC but rejected the handshake: {"code":-32000,"message":"the relay transport is not answering on this host"}

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

append_relayexistsget_relaylist_relayslist_replieswait_for_relay

Contract history

18 Sep 2026v0.1.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/p-e-relay-remote/badge.svg)](https://mcpi.app/servers/p-e-relay-remote)