--- title: "SubwayInfo NYC MCP server | Agent MCP Directory" description: "SubwayInfo NYC has an open MCP server with 26 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/subwayinfo-nyc site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # SubwayInfo NYC MCP server | Agent MCP Directory > SubwayInfo NYC has an open MCP server with 26 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/subwayinfo-nyc Site: Agent MCP Directory Last reviewed: 2026-11-05 # SubwayInfo NYC: MCP server, CLI and agent surfaces Yes: SubwayInfo NYC runs a public MCP server at subwayinfo.nyc that listed 26 tools to a client with no credentials on 4 November 2026. Examples: mta\_get\_arrivals, mta\_get\_line\_status, mta\_list\_alerts. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | SubwayInfo NYC | | --- | --- | | Domain | subwayinfo.nyc | | Category | Uncategorised (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for subwayinfo.nyc when asked on 5 November 2026 | | Company found through | the awesome-remote-mcp-servers list | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://subwayinfo.nyc/mcp | | --- | --- | | How it was found | listed in the awesome-remote-mcp-servers list | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | mta-subway-mcp-server 1.0.0 | | Capabilities | resources, tools, prompts | | Tools | 26 | | Resources | 2 | | Prompts | 3 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 332 ms over 1 attempt | ### Tools listed 26 tools - mta\_get\_arrivals - mta\_get\_line\_status - mta\_list\_alerts - mta\_search\_stations - mta\_get\_station\_info - mta\_get\_tunnel\_connectivity - mta\_plan\_trip - mta\_get\_planned\_work - bus\_list\_alerts - bus\_get\_arrivals - bus\_get\_route\_info - bus\_search\_stops - ferry\_get\_arrivals - ferry\_list\_alerts - ferry\_search\_landings - ferry\_get\_routes - bike\_get\_station\_status - bike\_search\_stations - bike\_get\_availability\_summary - rail\_get\_departures - rail\_list\_alerts - rail\_search\_stations - rail\_get\_station\_info - transit\_ask - search - fetch ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:44Z https://subwayinfo.nyc/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 790 ms - 20:04:41Z https://subwayinfo.nyc/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 332 ms ## Authentication | Auth type | No authentication | | --- | --- | | Auth as listed by a registry | Open (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Send the handshake to `https://subwayinfo.nyc/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for SubwayInfo NYC. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: subwayinfo.nyc (JSON, via a direct request). | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Yes: ckbk/subwayinfo-nyc | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/subwayinfo-nyc/index.md) ## Sources - [Where SubwayInfo NYC was found](https://github.com/jaw9c/awesome-remote-mcp-servers), read 4 November 2026 - [SubwayInfo NYC website](https://subwayinfo.nyc), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026