Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

p-e relay (remote)

by it-startversion 0.1.0i★ –iRuns in the cloud
Registry nameio.github.it-start/relay-ui

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://relay.zae.life/api/mcp

Run this in your terminal

claude mcp add --transport http relay-ui https://relay.zae.life/api/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://relay.zae.life/api/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account it-start, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32497 servers in this category
  • Published to the registry more recently than 45% of the other 32497 servers in this category
  • Basic checks equal to or better than 100% of the other 32497 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is p-e relay (remote) safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Zoo MCP

by KittyCAD

An MCP server that provides access to the Zoo API for various CAD operations and tools.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Agent Relay & Adjudication Protocol (v1.0-SPEC)

An industrial-grade, leaderless, multi-agent synchronization and dispute resolution protocol designed for autonomous LLM swarms (Claude, GPT-4o, Gemini, Mistral, and Human Architects).

Built upon canonical cryptographic digests (RFC 8785 / Proverbs 11:1), causal monotonicity (Hybrid Logical Clocks / HLC), atomic lock-free append ledgers (POSIX `O_CREAT | O_EXCL`), and adversarial cross-examination (Proverbs 18:17 Adjudication Court).


🏛️ Core Architectural Invariants (SPEC MUST 1–8)

  1. RFC 8785 JCS Canonicalization (MUST 1): Cryptographic SHA-256 digests are computed strictly on recursively sorted JSON keys, IEEE 754-normalized floats, and UTF-8 encoded payloads (*"A false balance is an abomination to the Lord, but a just weight is his delight" — Proverbs 11:1*).
  2. Hybrid Logical Clocks (MUST 2): Every envelope carries physical UTC time combined with a monotonic Lamport counter (physical_ms:counter:node_id) guaranteeing causal ordering across asynchronous nodes without NTP drift failure.
  3. Atomic Slot Allocation via `O_CREAT | O_EXCL` (MUST 3): Concurrent write races are resolved at the kernel filesystem level. If two agents attempt to claim the same sequence slot seq: N, the collision returns EEXIST, forcing the loser to increment seq monotonically.
  4. Adversarial Triad & Adjudication (MUST 4): No claim is ratified without adversarial cross-examination (*"The one who states his case first seems right, until the other comes and examines him" — Proverbs 18:17*).
  5. Zero Implicit Trust (MUST 5): Inter-agent envelopes must be verifiable offline and independently validated across different toolchains (TypeScript, Python, Rust, Go).
  6. Known-Missing Retention (MUST 6): When an envelope payload is purged/compacted or lost, the ledger retains its sequence slot, locator, and SHA-256 digest with status MISSING to prevent phantom slot re-use.
  7. Cross-Platform Rosetta Compatibility (MUST 7): Exact wire compatibility across JSON, YAML, Protocol Buffers, FlatBuffers, and MCP (Model Context Protocol).
  8. Real-time SSE & File Bus Streaming (MUST 8): Sub-millisecond reactive subscriptions via Server-Sent Events (SSE) and POSIX file watchers.

🚀 Quick Start

Prerequisites
  • Node.js 20+ (the scripts run under it; this is what the hosting container has)
  • Bun 1.1+ optional — a faster installer and runner for the same scripts
Installation & Run
# Clone the repository

git clone https://github.com/your-username/agent-relay.git cd agent-relay

Install dependencies — bun, because bun.lock is the lockfile here

bun install --frozen-lockfile

Start development server (Port 3000)

bun run dev

Build production bundle

bun run build bun run start

Open http://localhost:3000 to access the full Interactive Workbench, Live Relay Ledger, and Autonomous Agent Chat.

The commands above are bun, and the scripts they run stay Node-compatible on purpose. This is an AI Studio applet (metadata.json), and the hosting container invokes npm run build and npm start in a Node image with no `bun` on `PATH`. So npm is not a habit to be migrated away from here — it is what one real deployment target does, and package.json requires no binary either runtime lacks. CI keeps a node job for that reason and a bun job because O_CREAT | O_EXCL is implemented by each runtime for itself.

Everything this repository controls — deploy.sh, the contributor steps, the commands above — uses bun, and bun install --frozen-lockfile is the deterministic install: bun.lock is the only lockfile committed, and npm would write a second one that can disagree with it.

Environment
HOSTInterface to bind. Defaults to 127.0.0.1. This process authenticates nothing, so anything wider is a deliberate act and belongs behind a reverse proxy that does.
PORTDefaults to 3000.
NODE_ENVproduction serves the built client from dist/. Anything else starts a Vite dev server, which is not meant to face a network. bun run start sets it.
PE_STORE_ROOTRead an existing p-e relay store instead of this project's own. Read-only: write, delete and reset are declared unavailable and refused with 405.
ALLOW_SERVER_MODEL_CALLS1 enables the three routes that run models on API keys held by this process — /api/relay/adjudicate, /api/relay/step-triad, /api/relay/agent-exec — none of which has authentication of its own. Off by default. ALLOW_AGENT_EXEC is accepted as the former name.

📦 Project Structure

.

├── src/ │ ├── components/ │ │ ├── AgentChatInterface.tsx # Multi-agent chat with 1-click Triad & Court │ │ ├── LiveRelayConsole.tsx # Real-time ledger, sequencer & SSE observer │ │ ├── AdjudicationWorkbench.tsx # Court state machine (Proverbs 18:17) │ │ ├── RosettaMatrix.tsx # Cross-language wire serializers │ │ ├── EnvelopeStudio.tsx # RFC 8785 canonizer & digest generator │ │ ├── FailureSandbox.tsx # Chaos injection & invariant stress tests │ │ ├── BridgeExporter.tsx # MCP & Tool definitions export │ │ └── Navbar.tsx # Responsive top navigation │ ├── App.tsx # Root React 19 application │ ├── main.tsx # Vite React mount point │ └── index.css # Tailwind CSS & theme tokens ├── server.ts # Express + Atomic POSIX Store + SSE Hub ├── docs/ # Architecture specs & Engineering Backlog │ ├── ARCHITECTURE.md # In-depth architectural blueprint │ └── BACKLOG_AND_DEBT.md # Engineering insights, debt & roadmap ├── metadata.json # AI Studio runtime metadata ├── AGENTS.md # Context & rules for autonomous AI coding agents ├── CONTRIBUTING.md # Contribution guidelines ├── LICENSE # MIT License └── package.json # Build scripts & dependency declarations


🛠️ API & Wire Protocol

Envelope Specification
{

"seq": 42, "locator": "agent:claude/42@2026-09-01T16:45:00.000Z", "from": "agent:claude-code", "to": "agent:chatgpt-adversary", "type": "claim", "title": "HLC Monotonic Invariant Proposal", "parent_locator": "agent:human/41@2026-09-01T16:44:00.000Z", "hlc": "1788281100000:0001:claude", "digest": "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855", "payload": { "body": "Proposed RFC 8785 canonical digest validator." } }

Core HTTP Endpoints
  • POST /api/relay/deposit — Atomically deposit an envelope using O_CREAT | O_EXCL
  • GET /api/relay/records — Fetch current sequence ledger & envelope state
  • GET /api/relay/events — Real-time Server-Sent Events (SSE) feed
  • POST /api/relay/adjudicate — Execute Proverbs 18:17 Adjudication verdict via Gemini
  • POST /api/relay/agent-exec — Autonomous agent reasoning & response dispatcher

📜 Biblical & Mathematical Foundations

  • Proverbs 11:1: *"Dishonest scales are an abomination to the LORD, but a just weight is His delight."* — Foundational rule for bit-exact JSON Canonicalization (RFC 8785).
  • Proverbs 18:17: *"The first to state his case seems right, until another comes and examines him."* — Protocol mandate for adversarial cross-examination prior to ledger ratification.

📄 License

MIT License. Free for open-source research and enterprise distributed agent deployments.

Ask PopNx