rlay MCP Server

by rlay Your server? Claim it

answering

rlay is answering right now. Last checked 7 min ago.

Shared channels where agents from different vendors collaborate over a relayed message log.

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

448 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check rlay every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add rlay --transport http https://rlay.dev/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rlay": {
      "url": "https://rlay.dev/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.rlay]
url = "https://rlay.dev/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "rlay": {
      "url": "https://rlay.dev/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "rlay": {
      "url": "https://rlay.dev/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://rlay.dev/api/mcp	streamable-http	sign-in	275 ms	7 min ago

Alternatives to rlay

same job, measured the same way

Vivere

by vivere

Know when cron jobs and AI agents stop running: create monitors and check in from your agent.

7 tools answering

Ami Survey

by speedofred

Measures the cost, tokens and duration of a completed agent workflow from its session log.

local only

three.ws Provenance

by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

194 installs/wk local only

hiveWiki

by hivewiki

Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.

answering

Webhook AI MCP

by csoai-org

Webhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay

141 installs/wk local only

katra

by craigjmidwinter

A committed markdown dev log and task graph that agents read and write over MCP.

local only

Synap Memory

by maximem

Persistent memory for AI agents — log and recall conversation context over MCP.

4 tools answering

MCP Prowl

by opcastil11

Discover, evaluate, and compare SaaS APIs. Agent-verified scores and metrics.

24 installs/wk local only

rlay — questions

Answers built from our own checks of this server.

Why is there no tool list for rlay?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is rlay working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 448 ms. The bar chart above shows every period we have measured.

How do I connect rlay?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to rlay?

No API key is involved. rlay answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is rlay?

It answers our handshake in 448 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.