# Msha Mines (npm · @pipeworx/mcp-msha-mines)

MSHA mine records — search a US mine by operator or mine name, or look up a known MSHA Mine ID for…

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-msha-mines/msha-mines-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-msha-mines/msha-mines-mcp)
- npm · `@pipeworx/mcp-msha-mines`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines.md), [page](https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-msha-mines`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-msha-mines).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-msha-mines -- npx -y @pipeworx/mcp-msha-mines
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-msha-mines": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-msha-mines"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-msha-mines": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-msha-mines"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-msha-mines -- npx -y @pipeworx/mcp-msha-mines
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-msha-mines": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-msha-mines"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-msha-mines --command npx --arg -y --arg @pipeworx/mcp-msha-mines
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-msha-mines:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-msha-mines"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-msha-mines": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-msha-mines"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-msha-mines -t stdio -c npx -a -y @pipeworx/mcp-msha-mines
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-msha-mines": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-msha-mines"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +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.

### 2026-11-04 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-03 (score 81, +3)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `msha_mine_search` (~258 tokens)

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.

Input parameters:

- `limit` (number): Max mines to return (default 25, max 100).
- `query` (string, required): 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".

### `msha_mine_detail` (~200 tokens)

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.

Input parameters:

- `inspections_limit` (number): Max recent inspections to return (default 10, max 50).
- `mine_id` (string, required): 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).

### `msha_violation_counts` (~398 tokens)

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.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Msha Mines MCP server?

VerifyMCP ran 16 checks on Msha Mines, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-msha-mines
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-msha-mines
- Repository: https://github.com/pipeworx-io/mcp-msha-mines
- Website: https://pipeworx.io/packs/msha-mines
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-msha-mines/pipeworx-mcp-msha-mines