@pipeworx/mcp-msha-mines
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: gateway.pipeworx.io
What it contacted
gateway.pipeworx.io
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @pipeworx/mcp-msha-mines@0.2.1
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
msha_mine_search query, state, status, limit
Search MSHA (Mine Safety and Health Administration) mine records by operator name, controller name, or mine name. Returns matching mines with their MSHA Mine ID, status (Active, Abandoned, Intermittent, etc.), mine type (Surface/Underground/Facility), coal vs metal/non-metal classification, commodity, state, and current operator/controller. Use this to find the Mine ID(s) for a company before calling msha_mine_detail. Sourced from MSHA's own bulk mine-records file (public domain), refreshed weekly. Keyless.
msha_mine_detail mine_id, violations_limit, inspections_limit
Look up a known MSHA Mine ID: current status, type, commodity, operator and controller, plus recent inspections, recent violations (with assessed penalties, S&S flag, and abatement/termination dates), and recent quarterly employment and coal production. Violations/inspections/production cover only the most recent 5 calendar years (the response says so) — MSHA's full history back to 2000 is not loaded. Sourced from MSHA's own bulk mine-records files (public domain), refreshed weekly. Keyless.
msha_violation_counts mine_id, mine_name, year, year_from, year_to
Count MSHA violations issued at one mine within a calendar year or year range — in ONE call, not a listing. Returns the TOTAL plus a breakdown by who it was issued to (Operator vs Contractor vs Agent vs Miner) and by significant-and-substantial (S&S) status. Use this instead of msha_mine_detail when the question is "how many" — msha_mine_detail only returns its most recent violations_limit rows (default 20, max 100) and has no true count. Counted by the calendar year of each violation's own issue date (VIOLATION_ISSUE_DT, via MSHA's own CAL_YR field). Only the most recent 5 calendar years are loaded (the response's `coverage` field says exactly which); a year outside that window comes back flagged as "not loaded," never as a silent zero. Takes a known MSHA Mine ID (use msha_mine_search to find one) or a mine/operator/controller name — the name path only works when it resolves to exactly one mine; otherwise it lists the candidates so you can retry with a mine_id. Sourced from MSHA's own bulk mine-records files (public domain), refreshed weekly. Keyless.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/pipeworx-io/mcp-msha-mines |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-dS9dIobqrdf8xePM4RLCnylBqXXK5d++1dInKDR0VNv5cCpfqaOC/uKl2ikJxG/yLrllLU5zmiwjgX/6SR9VuQ== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pipeworx/mcp-msha-mines)
New version out? Ask for a fresh report.