Fra Rail Safety
NPM · @PIPEWORX/MCP-FRA-RAIL-SAFETY · 2 COMPONENTS
FRA Rail Safety — US railroad accidents and highway-rail grade crossing incidents reported to the…
Available components
Last scanned (10 hours ago)
Scores higher than 69% 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-fra-rail-safety). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1123 tokens (~374/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 77
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-fra-rail-safety@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-fra-rail-safety |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fra-rail-safety/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637318486 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7ea94612ace9d4564c02088d18c100947b410cc171c8fff7844d7363b315cfbfe6846db199e111e9df15d907a3590d367e61cefdfc6364552248615d6 |
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 →
crossing_incidents ~379
Highway-rail grade crossing collisions in the US — trains striking cars, trucks, pedestrians and cyclists at railroad crossings (FRA Form 57, 1975–present). Each incident carries the date, railroad, USDOT crossing id, state, county and city, road name, road user type and action (e.g. drove around gate, stopped on crossing), vehicle and train speed, crossing warning devices, weather, killed and injured. Newest first. Filter by state, county, city, year, railroad or a specific crossing id. Use for "railroad crossing accidents in Harris County Texas", "pedestrians hit by trains in California 2024", "incidents at crossing 812329E".
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, matched as a substring, e.g. "Houston". |
| county | string | – | County name, e.g. "Harris" (matched case-insensitively, "County" suffix optional). |
| crossing_id | string | – | USDOT grade crossing inventory number, e.g. "812329E". |
| fatal_only | boolean | – | Only incidents with at least one person killed. |
| highway_user | string | – | Road user type, matched as a substring: "Auto", "Truck", "Truck-trailer", "Pick-up truck", "Pedestrian", "Bus", "Motorcycle", "Van", "Other motor vehicle". |
| limit | number | – | Max incidents to return (default 25, max 200). |
| railroad | string | – | Railroad reporting-mark code ("UP", "BNSF") or part of its name. |
| state | string | – | US state as a two-letter code or full name, e.g. "TX" or "Texas". |
| year | number | – | Calendar year of the incident (1975–present). |
No output schema declared.
No examples provided.
rail_accident_summary ~268
Counts and totals of FRA-reported US railroad accidents or grade crossing incidents, grouped by railroad, cause, accident type, state, year or road user. Returns per-group incident count, killed, injured and (for train accidents) damage cost. Use for "which railroads had the most derailments in 2023", "top causes of train accidents in Texas", "crossing deaths per year since 2015", "rail accident trend by year".
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | "accidents" = rail equipment accidents (Form 54, default); "crossings" = highway-rail grade crossing incidents (Form 57). |
| from_year | number | – | Restrict to this year and later (use with group_by "year" for a trend). |
| group_by | string | yes | Grouping. "cause" and "accident_type" apply to accidents; "highway_user" to crossings; the rest to both. |
| limit | number | – | Max groups (default 20, max 100). |
| railroad | string | – | Restrict to one railroad (reporting-mark code or name substring). |
| state | string | – | Restrict to one US state (code or name). |
| year | number | – | Restrict to one calendar year. |
No output schema declared.
No examples provided.
rail_accidents ~417
US train accidents and derailments reported to the Federal Railroad Administration (FRA Form 54, 1975–present). Returns individual rail equipment accident reports — derailments, train collisions, obstruction and other impacts — with date, reporting railroad (e.g. UP, BNSF, CSX, NS, Amtrak), accident type, FRA primary cause code and description (e.g. H702 "Switch improperly lined", T110 "Wide gage"), state and county, train speed, hazmat cars released, people evacuated, killed, injured and damage cost. Newest first. Filter by year, state, railroad, cause code or accident type. Use for "train derailments in Ohio in 2023", "Norfolk Southern accidents", "rail accidents caused by broken rails".
| Name | Type | Req | Description |
|---|---|---|---|
| accident_type | string | – | Accident type text, matched as a substring: "Derailment", "Head on collision", "Rear end collision", "Side collision", "Raking collision", "Hwy-rail crossing", "Obstruction", "Fire/violent rupture",… |
| cause_code | string | – | FRA accident cause code or its prefix: "H702" exactly, or "T" for all track causes, "H" human factors, "E" equipment, "S" signal, "M" miscellaneous. |
| limit | number | – | Max reports to return (default 25, max 200). |
| min_damage_usd | number | – | Only accidents with total reported damage at or above this amount in US dollars. |
| railroad | string | – | Reporting railroad: a reporting-mark code ("UP", "BNSF", "CSX", "NS", "ATK") or part of its name ("Norfolk Southern"). |
| state | string | – | US state as a two-letter code or full name, e.g. "OH" or "Ohio". |
| year | number | – | Calendar year of the accident (1975–present), e.g. 2023. |
No output schema declared.
No examples provided.
How do I install the Fra Rail Safety MCP server?
Fra Rail Safety runs locally as an npm package, launched with npx -y @pipeworx/mcp-fra-rail-safety. 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-fra-rail-safety
claude mcp add pipeworx-io-fra-rail-safety -- npx -y @pipeworx/mcp-fra-rail-safety
What is the Fra Rail Safety MCP server?
Fra Rail Safety is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fra-rail-safety. FRA Rail Safety, US railroad accidents and highway-rail grade crossing incidents reported to the… This page covers its npm package (@pipeworx/mcp-fra-rail-safety).
Is the Fra Rail Safety MCP server safe to use?
Fra Rail Safety scores 81 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 Fra Rail Safety MCP server expose?
Fra Rail Safety exposes 3 tools: rail_accidents, crossing_incidents, rail_accident_summary. Their descriptions and schemas cost roughly 1,064 tokens of context every time the server is loaded.
Is the Fra Rail Safety MCP server still maintained?
Fra Rail Safety 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 Fra Rail Safety MCP server under?
Fra Rail Safety declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.