Msha Mines
NPM · @PIPEWORX/MCP-MSHA-MINES · 2 COMPONENTS
MSHA mine records — search a US mine by operator or mine name, or look up a known MSHA Mine ID for…
Available components
Last scanned (6 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
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-msha-mines). 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 912 tokens (~304/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.
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 +3
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-msha-mines@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-msha-mines |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-msha-mines/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655567135 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:752f5d2286eaadd7fcc5e3cce112c29f2941a975cae5dfbed5d22728347454dbf9702a5fa9a382fee2a5da2909c46ff22eb9652d4e739a2c23817ffa4 |
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 →
msha_mine_detail ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| inspections_limit | number | – | Max recent inspections to return (default 10, max 50). |
| mine_id | string | yes | MSHA Mine ID, e.g. "4608254". Find it with msha_mine_search if you only have an operator/mine name. |
| violations_limit | number | – | Max recent violations to return (default 20, max 100). |
No output schema declared.
No examples provided.
msha_mine_search ~258
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max mines to return (default 25, max 100). |
| query | string | yes | Operator, controller, or mine name (or part of one) to search for, e.g. "Peabody", "Warrior Met Coal", "O'Neal Quarry". |
| state | string | – | Optional 2-letter US state code to restrict the search, e.g. "WV", "KY". |
| status | string | – | Optional exact mine status filter: Active, Abandoned, "Abandoned and Sealed", Intermittent, "New Mine", NonProducing, "Temporarily Idled". |
No output schema declared.
No examples provided.
msha_violation_counts ~398
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mine_id | string | – | MSHA Mine ID, e.g. "4601437". Preferred over mine_name — unambiguous. |
| mine_name | string | – | Mine, operator, or controller name to resolve to a Mine ID — used only when mine_id is omitted, and only works if it matches exactly one mine. |
| year | number | – | Single calendar year to count, e.g. 2025. |
| year_from | number | – | First calendar year of a range (inclusive). Use together with year_to instead of year. |
| year_to | number | – | Last calendar year of a range (inclusive). Use together with year_from instead of year. |
No output schema declared.
No examples provided.
How do I install the Msha Mines MCP server?
Msha Mines runs locally as an npm package, launched with npx -y @pipeworx/mcp-msha-mines. 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-msha-mines
claude mcp add pipeworx-io-msha-mines -- npx -y @pipeworx/mcp-msha-mines
What is the Msha Mines MCP server?
Msha Mines is an MCP server listed in the public MCP registry as io.github.pipeworx-io/msha-mines. MSHA mine records, search a US mine by operator or mine name, or look up a known MSHA Mine ID for… This page covers its npm package (@pipeworx/mcp-msha-mines).
Is the Msha Mines MCP server safe to use?
Msha Mines scores 82 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 Msha Mines MCP server expose?
Msha Mines exposes 3 tools: msha_mine_search, msha_mine_detail, msha_violation_counts. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.
Is the Msha Mines MCP server still maintained?
Msha Mines 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 Msha Mines MCP server under?
Msha Mines declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.