Marketing · Official remote MCP server

The p-e relay (remote) MCP server,
connected in one click.

Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed. Connect the official p-e relay (remote) MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Free to start · No credit card · No hosting needed

Use this server

Add p-e relay (remote) to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http p-e-relay-remote https://relay.zae.life/api/mcp

Run in your terminal, then restart Claude Code.

p-e relay (remote) · https://relay.zae.life/api/mcp

What you can do

What your AI can do with p-e relay (remote)

Real prompts you can type the moment it's connected — no setup, no docs to read.

“Use “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.”

“Use “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 prove.”

“Use “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.”

“Use “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.”

Security check

How secure is the p-e relay (remote) MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how p-e relay (remote) holds up.

✓ Verified directory serverp-e relay (remote) · zae.life

Official endpoint

Operated by p-e relay (remote) (zae.life) at its documented MCP endpoint — not a third-party mirror or community re-host.

No sign-in needed

This server only exposes public data — no account and no credentials are involved when you connect.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If p-e relay (remote) adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

How it works

Connected in three steps

01

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

02

Pick p-e relay (remote)

Choose p-e relay (remote) in the gate directory. No sign-in needed.

03

Use it anywhere

p-e relay (remote)'s tools are live in every AI client you've connected — with rules and logging built in.

Connect p-e relay (remote) free

Free to start · No credit card · No hosting needed

Straight from the server

The actual tools p-e relay (remote) exposes

Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.

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

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 prove

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.

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

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 t

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

Author

Who runs the p-e relay (remote) MCP server?

Server facts

The p-e relay (remote) MCP server at a glance

Endpointhttps://relay.zae.life/api/mcp
Operated byp-e relay (remote) (zae.life)
CategoryMarketing
Sign-inNone — public data only
Available in gateYes — one-click connect
Works withClaude, ChatGPT, Cursor & any MCP client
FAQ

Questions, answered

Is there an official p-e relay (remote) MCP server?

Yes — p-e relay (remote) operates its own remote MCP server at relay.zae.life. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect p-e relay (remote) to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick p-e relay (remote) in the directory. No account or sign-in is needed. From then on, p-e relay (remote)'s tools are available in every client you've connected to gate.

Do I need to host anything?

No. p-e relay (remote) runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

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

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.

Is it free?

Yes — you can get started with gate for free and connect p-e relay (remote) in minutes. No credit card required.

More servers

Connect more than just p-e relay (remote)

Every server below works through the same gateway URL — connect once, add tools anytime.

Set up p-e relay (remote) in: Claude · Claude Code · ChatGPT · Cursor · VS Code

Give your AI p-e relay (remote) — safely.

One URL. All MCPs. Full control. Free to start.

Get started free