Sign-in required, tools not seen, not counted. The MCP endpoint listed for Railway at mcp.railway.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
89, grade A; Ora scanned the domain on 25 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for railway.com, a vendor-published score)
Company found through
the vendor's own documentation; the official MCP Registry
Last verified
4 November 2026
MCP server
Endpoint
https://mcp.railway.com/
How it was found
listed in the vendor's own documentation; the official MCP Registry
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
19:59:05Z https://mcp.railway.com/ sent initialize result auth-required (HTTP 401) 829 ms
20:04:11Z https://mcp.railway.com/ sent initialize result auth-required (HTTP 401) 726 ms
Request https://mcp.railway.com/ without a token. It answers 401 and a WWW-Authenticate header.
Read the protected resource metadata at https://mcp.railway.com/.well-known/oauth-protected-resource to find the authorization server.
Register a client at the registration endpoint https://backboard.railway.com/oauth/register (dynamic client registration), so no human has to create an app first.
Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.