_ registry / mcp http-sse · checked 2h ago

transit-mcp

https://transitmcp.com

Registry code: aaa74cc6fbc1f7ce

api record

Read-only, real-time transit data for the Washington DC Metro (city "dc", WMATA) and the New York City Subway (city "nyc", MTA).

For train arrivals call get_station_predictions with a station name or ID. When a name matches several stations, choose from the candidates offered or call search_stations and retry with the exact station ID.

endpoint
https://transitmcp.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is transit-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is transit-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does transit-mcp have?
13 tools: get_train_positions, get_route_info, get_station_predictions, search_stations, get_stations_by_line, get_all_stations, get_station_transfers, get_incidents, ….
Is transit-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
667ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 13 tools
3 open 10 never probed 3 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_bus_positions open 2h ago

    Get real-time positions of DC Metro buses, optionally filtered by route.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "routeId": {
      "type": "string",
      "description": "Optional route ID filter (e.g., \"30N\"). Omit for all buses."
    }
  }
}
    arguments 10 lines
  • get_bus_routes open 2h ago

    Get all DC Metro bus routes with route IDs and descriptions.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_bus_stops open 2h ago

    Get DC Metro bus stops. Returns all stops or filters by lat/lon/radius.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "radius": {
      "type": "number",
      "description": "Search radius in meters"
    },
    "latitude": {
      "type": "number",
      "description": "Center latitude for geographic search"
    },
    "longitude": {
      "type": "number",
      "description": "Center longitude for geographic search"
    }
  }
}
    arguments 18 lines
  • get_train_positions unknown never probed

    Get real-time positions of all trains on the DC Metro system.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • get_route_info unknown never probed

    Get detailed information about a transit route including service patterns. NYC Subway only.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city",
    "routeId"
  ],
  "properties": {
    "city": {
      "enum": [
        "nyc"
      ],
      "type": "string"
    },
    "routeId": {
      "type": "string",
      "description": "Route identifier — NYC: A, B, C, D, E, F, M, G, J, Z, L, N, Q, R, W, 1, 2, 3, 4, 5, 6, 7, SI"
    }
  }
}
    arguments 20 lines
  • get_station_predictions unknown never probed

    Get real-time train arrival predictions for a transit station. Supports DC Metro and NYC Subway. Accepts a station name or an exact station ID; if a name matches several stations, the result lists the candidates to choose from.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city",
    "stationName"
  ],
  "properties": {
    "city": {
      "enum": [
        "dc",
        "nyc"
      ],
      "type": "string"
    },
    "stationName": {
      "type": "string",
      "description": "Station name (e.g., \"Metro Center\", \"Times Square\") — auto-converted to station ID. DC accepts codes like \"A01\"."
    }
  }
}
    arguments 21 lines
  • search_stations unknown never probed

    Search for transit stations by name or code. Supports DC Metro and NYC Subway.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city",
    "query"
  ],
  "properties": {
    "city": {
      "enum": [
        "dc",
        "nyc"
      ],
      "type": "string"
    },
    "query": {
      "type": "string",
      "description": "Search query (station name or code)"
    }
  }
}
    arguments 21 lines
  • get_stations_by_line unknown never probed

    Get all stations on a specific transit line. Supports DC Metro and NYC Subway.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city",
    "lineCode"
  ],
  "properties": {
    "city": {
      "enum": [
        "dc",
        "nyc"
      ],
      "type": "string"
    },
    "lineCode": {
      "type": "string",
      "description": "Line code — DC: RD, BL, YL, OR, GR, SV | NYC: 1-7, A, C, E, B, D, F, M, N, Q, R, W, J, Z, L, G, SI"
    }
  }
}
    arguments 21 lines
  • get_all_stations unknown never probed

    Get the complete list of transit stations with coordinates for one city. Large result; prefer search_stations or get_stations_by_line when looking for specific stations.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "enum": [
        "dc",
        "nyc"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_station_transfers unknown never probed

    Get transfer connections and nearby stations from a transit station. NYC Subway only.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city",
    "stationId"
  ],
  "properties": {
    "city": {
      "enum": [
        "nyc"
      ],
      "type": "string"
    },
    "stationId": {
      "type": "string",
      "description": "Station ID (e.g., \"127\" for Times Square)"
    }
  }
}
    arguments 20 lines
  • get_incidents unknown never probed

    Get current transit incidents and service advisories for DC Metro or NYC Subway.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "enum": [
        "dc",
        "nyc"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_elevator_incidents unknown never probed

    Get current elevator and escalator outages. DC Metro only.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "enum": [
        "dc"
      ],
      "type": "string"
    }
  }
}
    arguments 15 lines
  • get_bus_predictions unknown never probed

    Get real-time bus arrival predictions for a DC Metro bus stop.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "stopId"
  ],
  "properties": {
    "stopId": {
      "type": "string",
      "description": "DC Metro 7-digit regional bus stop ID (e.g., \"1001195\")"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id aaa74cc6fbc1f7ce.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aaa74cc6fbc1f7ce/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aaa74cc6fbc1f7ce/badge.svg)](https://brick.blue/agent/aaa74cc6fbc1f7ce?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.