Toronto and GTA Transit MCP server
ca.sitesy/transitsitesy.castreamable-httpv1.3.0Scanned
Live TTC, Hamilton HSR, GO Transit and UP Express stops, departures, alerts and vehicle positions.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Toronto and GTA Transit MCP server can do
The Toronto and GTA Transit MCP server is published by sitesy.ca, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
next_departuresGet the next departures for one stop on the TTC, Hamilton HSR or GO Transit, including UP Express stations.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get the next departures for one stop on the TTC, Hamilton HSR or GO Transit, including UP Express stations. 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, the Metrolinx Open Data API for GO and UP Express), and realtime entries replace matching scheduled entries. Stop ids can collide between agencies: pass agency to say which agency the stop belongs to. Without agency, a stop id that exists in more than one agency returns an error naming every match instead of guessing.
route_vehiclesGet live vehicle positions for one route from the agency GTFS Realtime vehicle positions feed.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get live vehicle positions for one route from the agency GTFS Realtime vehicle positions feed. Pass agency to resolve the route inside one agency. For GO Transit the route can be a line short name or long name such as LW or Lakeshore West, a bus route number such as 41, or UP for UP Express trains. Without agency the TTC is tried first, then HSR, then GO Transit, so a route name that exists in more than one agency returns the first match in that order.
search_stopsFind transit stops and stations by stop number, stop code, or name from the static GTFS feeds.No findings
Why it is in this group
- The name "search_stops" says "search": a word for reading.
Description, as the server wrote it Find transit stops and stations by stop number, stop code, or name from the static GTFS feeds. Searches the TTC, Hamilton HSR and GO Transit by default and merges the results; pass agency to search one agency only. Every result carries an agency field (TTC, HSR or GO). GO Transit results include the UP Express stations Union Station, Bloor, Weston and Pearson Airport.
service_alertsGet currently active service alerts.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get currently active service alerts. Defaults to the TTC, optionally filtered by mode to subway, bus, streetcar, or accessibility alerts; the mode filter applies to TTC alerts only. Pass agency hsr for Hamilton HSR alerts, agency go for GO Transit and UP Express alerts, or agency all for every agency combined.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:next_departuresOnly readsdescriptioninputSchema
- Changed:route_vehiclesOnly readsdescriptioninputSchema
- Changed:search_stopsOnly readsdescriptioninputSchema
- Changed:service_alertsOnly readsdescriptioninputSchema
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http transit https://transit.sitesy.ca/mcpclaude mcp add --transport http transit https://transit.sitesy.ca/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__transit__search_stops",
"mcp__transit__next_departures",
"mcp__transit__service_alerts",
"mcp__transit__route_vehicles"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as transit. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ca.sitesy/transit/verify?hash=c5e34f72c4fd3a674f41b9c8b6afdcbd8f14251fcf9572a967483830e3e0c094" | jq -e '.changed == false'Pinned hash c5e34f72c4fd, from Nov 20, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ca.sitesy/transit/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ca.sitesy/transit)Source: MCP Registry. Synced Nov 20, 2026, 19:17 UTC.
Toronto and GTA Transit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Toronto and GTA Transit MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Toronto and GTA Transit MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Toronto and GTA Transit MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Toronto and GTA Transit MCP server have?
- 4 tools: 4 read. search_stops, next_departures, service_alerts and route_vehicles.
Does the Toronto and GTA Transit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Toronto and GTA Transit MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Toronto and GTA Transit MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.