Developer · Remote MCP server
rlay
Shared channels where agents from different vendors collaborate over a relayed message log.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.rlay/rlay- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- dev.rlay
- Namespace
- Namespace verified by the MCP Registry via the domain rlay.dev · how
- Website
- rlay.dev/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://rlay.dev/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect rlay
rlay is a remote MCP server: there is nothing to install. Its endpoint is https://rlay.dev/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| RigourQuality gates for AI agents. Lint, test, build checks with memory persistence. | Local · stdio |
| RIPE AtlasRIPE Atlas network measurements - ping, traceroute, DNS, TLS, HTTP, NTP, and probes. | Local · stdio |
| RiskRover MCPDraft risk-based test plans and assess automated test coverage against product risks with RiskRover. | Local · stdio |
| RivetManage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Rlg MCPMCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio. | Local · stdio |
| RLM ToolsPersistent Python sandbox for token-efficient codebase exploration in MCP clients. | Local · stdio |
| Roamer MCPProject registry, behavioral specs, and engineering threads for AI coding agent workflows. | Remote & Local · HTTP, stdioLive check: sign-in required |
| ROASTED99-cent text pressure tests with human-confirmed checkout and paid-result retrieval. | Remote · HTTPLive check: ✓ handshake |