`msha_mine_detail`

Pack: msha-mines · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/msha_mine_detail for the schema, then POST the same URL with its arguments for the data.

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.

Parameters

Name	Type	Required	Description
`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	no	Max recent violations to return (default 20, max 100).
`inspections_limit`	number	no	Max recent inspections to return (default 10, max 50).

Example call

Arguments

{
  "mine_id": "0100003"
}

curl

curl -X POST https://gateway.pipeworx.io/msha-mines/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"msha_mine_detail","arguments":{"mine_id":"0100003"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('msha_mine_detail', {
  "mine_id": "0100003"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the msha-mines pack

{
  "mcpServers": {
    "msha-mines": {
      "url": "https://gateway.pipeworx.io/msha-mines/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

msha_mine_detail