Toronto and GTA Transit
v1.2.0Live TTC and Hamilton HSR transit: stop search, next departures, service alerts, vehicle positions.
Endpoint health
online- Last checked
- 11/20/2026, 6:17:04 AM
- Latency
- 140 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ca.sitesy%2Ftransit
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ca.sitesy/transit": {
"url": "https://transit.sitesy.ca/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
next_departures
Get the next departures for one stop on the TTC or Hamilton HSR. Static schedule candidates from the persistent schedule store are merged with GTFS Realtime trip updates (BusTime for the TTC, the City of Hamilton feed for HSR), and realtime entries replace matching scheduled entries. TTC and HSR stop ids can collide: pass agency to say which agency the stop belongs to. Without agency, a stop id that exists in both agencies returns an error naming both matches instead of guessing.
Schema valid · SHA-256 dbf4bcbaa122…
View input schema
{ "type": "object", "properties": { "stop_id": { "type": "string", "minLength": 1, "description": "A stop_id from search_stops. A parent station includes its child stops." }, "agency": { "description": "Optional agency the stop belongs to: ttc or hsr. Required when the stop id exists in both agencies.", "type": "string", "enum": [ "ttc", "hsr" ] }, "limit": { "default": 10, "description": "Maximum departures to return", "type": "integer", "minimum": 1, "maximum": 30 } }, "required": [ "stop_id" ], "$schema": "http://json-schema.org/draft-07/schema#" }route_vehicles
Get live vehicle positions for one route from the agency GTFS Realtime vehicle positions feed. Pass agency to resolve the route inside one agency. Without agency the TTC is tried first and HSR second, so a route name that exists in both returns the TTC vehicles.
Schema valid · SHA-256 727cfa87cffb…
View input schema
{ "type": "object", "properties": { "route": { "type": "string", "minLength": 1, "description": "A route_id, short name, or long name, for example 501, King, or 1" }, "agency": { "description": "Optional agency the route belongs to: ttc or hsr", "type": "string", "enum": [ "ttc", "hsr" ] }, "limit": { "default": 50, "description": "Maximum vehicles to return", "type": "integer", "minimum": 1, "maximum": 200 } }, "required": [ "route" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://transit.sitesy.ca/mcp