Agent MCP Directory

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

CompanySubwayInfo NYC
Domainsubwayinfo.nyc
CategoryUncategorised (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora scorenone: Ora returned no cached score for subwayinfo.nyc when asked on 5 November 2026
Company found throughthe awesome-remote-mcp-servers list
Last verified4 November 2026

MCP server

Endpointhttps://subwayinfo.nyc/mcp
How it was foundlisted in the awesome-remote-mcp-servers list
Transportstreamable-http
HTTP status200
Protocol version2025-11-25
Servermta-subway-mcp-server 1.0.0
Capabilitiesresources, tools, prompts
Tools26
Resources2
Prompts3
Connected4 November 2026, 20:04 UTC
Handshake time332 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 typeNo authentication
Auth as listed by a registryOpen (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 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.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileFound: subwayinfo.nyc (JSON, via a direct request).
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot 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.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversYes
SmitheryYes: ckbk/subwayinfo-nyc
GlamaNot checked: Glama's API needs a key and attribution terms.