La Metro
NPM · @PIPEWORX/MCP-LA-METRO · 2 COMPONENTS
LA Metro (LACMTA) MCP — routes, stops and live service cancellations for Los Angeles County Metro…
Available components
Last scanned (10 hours ago)
Scores higher than 81% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-la-metro). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 578 tokens (~144/item across 4 items; 4 tools + 0 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 81
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-la-metro@0.2.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-la-metro |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-la-metro/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649607163 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:25feab46bf3eb4ce818bda024c03c816a40f8b4ee28e811f3637107de182d0dfda70d1e4826d2909190e9f46fde6581917afea170a0edbc08c75d18af |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
lametro_route_stops ~152
Every stop served by one LA Metro route, in running order, with stop id, name, direction and service day type. AUTHORITATIVE for "which stops does route N serve" and for turning a route into stop ids you can look up with lametro_stop.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | 'LACMTA' (bus, default) or 'LACMTA_Rail'. |
| direction_id | number | – | Optional: keep only direction 0 or 1. |
| route_code | string | yes | Route code from lametro_routes — a number for bus (e.g. "10", "720"), or a line name for rail (e.g. "Metro A-Line"). |
No output schema declared.
No examples provided.
lametro_routes ~151
Every LA Metro bus or rail route, with its route code, short and long name, direction description and map colour. AUTHORITATIVE for "what routes does LA Metro run" — sourced from LACMTA's own API, not a third-party scrape. Use the returned route_code as input to lametro_route_stops.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | 'LACMTA' for bus (default, ~124 routes) or 'LACMTA_Rail' for the rail and busway lines (A/B/C/D/E/K, ~6). |
| search | string | – | Optional case-insensitive filter over route name and description (e.g. "Wilshire", "Rapid"). |
No output schema declared.
No examples provided.
lametro_service_cancellations ~125
Trips LA Metro has canceled on the current service day, counted per route. This is LIVE operational data and the one real-time signal LACMTA publishes publicly — AUTHORITATIVE for "is LA Metro dropping trips on my line today", which no schedule or GTFS feed can answer. Sorted worst-affected first.
| Name | Type | Req | Description |
|---|---|---|---|
| min_canceled | number | – | Optional: only report routes with at least this many canceled trips. |
| route_code | string | – | Optional: report only this route code (e.g. "251"). Omit for every affected route. |
No output schema declared.
No examples provided.
lametro_stop ~96
One LA Metro stop by stop id — coordinates, name, and the accessibility and zone attributes LACMTA publishes for it. Returns GeoJSON properties flattened for reading.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | 'LACMTA' (bus, default) or 'LACMTA_Rail'. |
| stop_id | string | yes | Numeric stop id, as returned by lametro_route_stops (e.g. "3202"). |
No output schema declared.
No examples provided.
How do I install the La Metro MCP server?
La Metro runs locally as an npm package, launched with npx -y @pipeworx/mcp-la-metro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-la-metro
claude mcp add pipeworx-io-la-metro -- npx -y @pipeworx/mcp-la-metro
What is the La Metro MCP server?
La Metro is an MCP server listed in the public MCP registry as io.github.pipeworx-io/la-metro. LA Metro (LACMTA) MCP, routes, stops and live service cancellations for Los Angeles County Metro… This page covers its npm package (@pipeworx/mcp-la-metro).
Is the La Metro MCP server safe to use?
La Metro scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 La Metro MCP server expose?
La Metro exposes 4 tools: lametro_routes, lametro_route_stops, lametro_stop, lametro_service_cancellations. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.
Is the La Metro MCP server still maintained?
La Metro is still listed as active in the MCP registry. We last reached this channel on 5 November 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 La Metro MCP server under?
La Metro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the La Metro MCP server?
VerifyMCP ran 16 checks on La Metro, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.