Other · Remote MCP server
Waitloop
Agent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.zexiro/waitloop- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-05
- Updated
- 2026-07-05
- Publisher
- zexiro (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/zexiro) · how
- Website
- waitloop.dev
- Repository
- github.com/zexiro/waitloop
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://waitloop.dev/api/mcp | Authorization (required, 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
- No - TLS handshake failed
- Handshake
- -
- Checked on
- 2026-10-05
How to connect Waitloop
Waitloop is a remote MCP server: there is nothing to install. Its endpoint is https://waitloop.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.
The registry entry declares an HTTP header for the connection: Authorization (required, 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
More other servers
| Server | Runs |
|---|---|
| Waggle MCPPersistent graph-backed conversational memory for AI agents. | Local · stdio |
| WAGO PLCRead and monitor WAGO PLC parameters over the WDA REST API. Read-only unless writes are allowed. | Local · stdio |
| WaitingForPowerTracks U.S. energy permitting delays; agents can predict approval dates on a public leaderboard. | Remote · HTTPLive check: ✓ handshake |
| WaitlisterCreate waitlists, landing pages, manage subscribers, referrals, and view stats on Waitlister. | Local · stdio |
| WAKE ProtocolA post-mortem succession protocol for AI agents. Black Box, handoff, time-locks. | Local · stdio |
| Wakeonlan MCP ServerWake LAN machines with Wake-on-LAN magic packets from host profiles, then confirm they came up. | Local · stdio, HTTP |
| Walk-Forward ValidatorWalk-Forward Efficiency, parameter-stability scoring, and WFO window generation. | Remote · HTTPLive check: sign-in required |
| WalkscoreWalk Score MCP - wraps the Walk Score API (walkscore.com) | Remote · HTTPLive check: ✓ handshake |