Other · Remote MCP server
AlfaNest Relay
Hosted bus for AI agents: lock, events, reject. Publish/apply stay on the sidecar.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.alfanestlabs/relay- Version
- 0.1.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-12
- Updated
- 2026-09-12
- Publisher
- com.alfanestlabs
- Namespace
- Namespace verified by the MCP Registry via the domain alfanestlabs.com · how
- Website
- relay.alfanestlabs.com
- Repository
- github.com/alfanestlabs/alfanest-relay
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://relay.alfanestlabs.com/mcp | Authorization (secret) |
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 AlfaNest Relay
AlfaNest Relay is a remote MCP server: there is nothing to install. Its endpoint is https://relay.alfanestlabs.com/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.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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
Site checks
The website's own root, relay.alfanestlabs.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | Real file, HTTP 200 · 2026-10-04 |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| AlertsBarDomain exposures: breaches, infostealers, ULP heap, cookies. Counts and samples, free. | Remote · HTTPLive check: ✓ handshake |
| ALEX Evidence VerifyVerify signed ALEX Evidence Packages. Fails closed on signature or schema errors. | Local · stdio |
| Alex Polonsky ProfilePublic, read-only professional profile and current availability for Alex Polonsky. | Remote · HTTPLive check: ✓ handshake |
| Alfabot MCP ServerConsulta de planes de productos Alfabot y agendamiento de reuniones para colegios y empresas. | Remote · HTTPLive check: ✓ handshake |
| AlfilAlfil MCP: politicos, partidos, contratacion SECOP y datos electorales de Colombia, gratis. | Remote · HTTPLive check: sign-in required |
| Algorand MCPAlgorand chain status from the public indexer. No key required. | Local · stdio |
| Alice - Santé territoriale France CareDonnees sante territoriale France: acces aux soins, FINESS, RNA - 35 000+ communes. | Remote · HTTPLive check: ✓ handshake |
| Alienvault OtxAlienVault OTX MCP - Open Threat Exchange (free with key) | Remote · HTTPLive check: ✓ handshake |