com.getrailhq/demorail
Demorail
Is the Demorail MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Interactive product demos: list demos and steps, make prospect links, read leads and drop-off.
needs auth probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Sign in with your Railhq account"}}- Endpoint
- https://mcp.getrailhq.com/mcp (streamable-http)
- Host
- mcp.getrailhq.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.getrailhq.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server accounts.getrailhq.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:token-exchange.
Scopes mcp openid email profile offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://demorail.com
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention interactive or prospect.
- ai.backengine/backengine-mcp · needs auth
- ai.enginy/mcp · needs auth
- Klarix Intelligence Engine ai.klarix/intelligence · alive
- Banking Assistant (Metabind demo) ai.metabind/banking-assistant · alive
- Lead Intelligence ai.saifs/lead-intelligence · needs auth
- Learn with Agents app.learnwithagents/learn-with-agents · needs auth
- Marketgenius app.marketgenius/mcp · alive
- Race Calendar F1 app.racecalendar/f1 · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.