Charlotte Area Transit (CATS)
PYPI · QUEENSCOACH · 2 COMPONENTS
CATS bus and light rail trip planning, live arrivals, timetables, routes, and service alerts
Available components
Last scanned (20 hours ago)
Scores higher than 96% of PyPI servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ajwann/queenscoach). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1755 tokens (~117/item across 15 items; 7 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 −1
- Stability: pass → 0.87 functional
- 15 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 14 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 13 Oct 26 +18
- Malware scan: unverified → pass ▲ security
- Stability: fail → 0.93 functional
- 12 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 47.
- 4 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Oct 26 −14
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed pypi/queenscoach@2.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ajwann/queenscoach |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ajwann/queenscoach/.github/workflows/release.yml@refs/tags/v2.1.1 |
| Rekor log index | 2901477802 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4d56fdc0010161cb2b592313320fd615094e1515bf3b1a20b606efee6aa87624 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_arrivals Get arrival times at a stop ~169
Estimated arrival times of buses or trains at one stop or station. Give "stop" (a stop id, stop code, or part of a stop name), or, for "my stop" / "near me" questions, the user's current device location as latitude and longitude to use the nearest station. With a location, "mode" or "route" picks the nearest stop that service actually calls at, so asking for trains finds the nearest rail station rather than a closer bus stop. Reports minutes away, schedule deviation, the vehicle number, and any service alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | – | – | – |
| limit | – | – | Maximum arrivals to return. |
| longitude | – | – | – |
| mode | – | – | Only show bus or train arrivals. |
| route | – | – | Only show arrivals for this route. |
| stop | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_route Describe a route ~144
Everything about one CATS route on a date: for each direction, where it goes, its stops in order, its first and last trips, and how often it runs in the early morning, morning rush, midday, afternoon rush, evening, and late night. Also how many trips run on each of the next seven days, and how many service alerts are active. Use it for 'where does the Blue Line go' or 'how often does the 9 run on Saturday' (pass that Saturday's date).
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | – |
| route | string | yes | Route number or name, e.g. "9", "501", "Blue Line", "Airport". |
Structured output declared, but exposes no named fields.
No examples provided.
get_schedule Get the timetable at a stop ~183
The published timetable at one stop or station for a date: scheduled departures with each trip's route and real destination, and the first and last departure that day. Use it for 'when is the last train tonight', 'does this bus run on Sunday', or times later today or on another date; use get_arrivals instead for live predictions in the next hour. Give "stop", or the user's location as latitude and longitude for the nearest stop serving the route or mode. Times default to from now (today) or the start of service (other dates).
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| before | – | – | – |
| date | – | – | – |
| latitude | – | – | – |
| limit | – | – | Maximum departures to list (default 20). |
| longitude | – | – | – |
| mode | – | – | Only bus or train departures. |
| route | – | – | Only departures on this route. |
| stop | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_service_alerts Get service alerts ~100
Current and upcoming CATS service alerts: detours, closed stops, and suspended service, with what is affected, why, and until when. Give "route" or "stop" to narrow them, the user's location as latitude and longitude for alerts affecting stops within 800 m, or nothing for every alert in the system.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | – | – | – |
| longitude | – | – | – |
| route | – | – | Alerts affecting this route. |
| stop | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_stops Find stops and stations ~208
CATS stops and stations with the bus routes and light rail lines serving each (501 is the LYNX Blue Line, 510 the CityLYNX Gold Line). For "closest station" or "near me" questions, pass the user's current device location as latitude and longitude; results are then nearest first with metersAway. Narrow with "mode" (e.g. train for the nearest rail station), "route", or "query" (part of a name). Same-named platforms close together are returned as one station. The complete raw stop table is the gtfs://static/stops.txt resource.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | – | – | – |
| limit | – | – | Maximum stations to return (default 10 with a location, 250 without). |
| longitude | – | – | – |
| mode | – | – | Only stops with bus or train service. |
| query | – | – | Stop id, stop code, or part of a stop name, e.g. "Tryon". |
| route | – | – | Only stops this route serves. |
Structured output declared, but exposes no named fields.
No examples provided.
list_vehicles Find buses and trains ~121
Current GPS positions of CATS buses and trains in service. Give "vehicle" to locate one bus or train by its number (e.g. "2301"), "route" for every vehicle on a route (e.g. "9", "501", "Blue Line"), "mode" for buses or trains, or nothing for the whole system. Includes heading, speed, occupancy, headsign, and the next stop when available.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Maximum vehicles to return. |
| mode | – | – | – |
| route | – | – | – |
| vehicle | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
plan_trip Plan a trip ~257
Plan a trip on CATS buses and trains between two places, with walking at either end and between stops. Give the start as origin_stop or origin_latitude and origin_longitude (use the user's current device location for 'from here'), and the destination the same way (look up a venue's or address's coordinates first). Leave now by default, or give depart_at or arrive_by with an optional date. Returns up to 3 itineraries: each ride's route, where to board and get off, the vehicle's destination, times including live delays when a vehicle is reporting, wait at each transfer, and walking legs. Walking is estimated from straight-line distance.
| Name | Type | Req | Description |
|---|---|---|---|
| arrive_by | – | – | – |
| date | – | – | – |
| depart_at | – | – | – |
| destination_latitude | – | – | – |
| destination_longitude | – | – | – |
| destination_stop | – | – | Destination stop id, code, or name. |
| max_transfers | – | – | Most vehicle changes allowed (default 2). |
| max_walk_meters | – | – | Longest walk to the first stop or from the last, in meters (default 800). |
| origin_latitude | – | – | – |
| origin_longitude | – | – | – |
| origin_stop | – | – | Starting stop id, code, or name. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Charlotte Area Transit (CATS) MCP server?
Charlotte Area Transit (CATS) runs locally as a PyPI package, launched with uvx queenscoach. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · queenscoach
claude mcp add ajwann-queenscoach -- uvx queenscoach
What is the Charlotte Area Transit (CATS) MCP server?
Charlotte Area Transit (CATS) is an MCP server listed in the public MCP registry as io.github.ajwann/queenscoach. CATS bus and light rail trip planning, live arrivals, timetables, routes, and service alerts. This page covers its PyPI package (queenscoach).
Is the Charlotte Area Transit (CATS) MCP server safe to use?
Charlotte Area Transit (CATS) scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Charlotte Area Transit (CATS) MCP server expose?
Charlotte Area Transit (CATS) exposes 7 tools: list_vehicles, list_stops, get_arrivals, plan_trip, get_schedule, and 2 more. Their descriptions and schemas cost roughly 1,182 tokens of context every time the server is loaded.
Is the Charlotte Area Transit (CATS) MCP server still maintained?
Charlotte Area Transit (CATS) is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Charlotte Area Transit (CATS) MCP server under?
Charlotte Area Transit (CATS) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.