# Dol Whd (npm · @pipeworx/mcp-dol-whd)

DOL Wage & Hour Division — concluded enforcement cases

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

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-dol-whd/dol-whd-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-dol-whd/dol-whd-mcp)
- npm · `@pipeworx/mcp-dol-whd`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-dol-whd/pipeworx-mcp-dol-whd.md), [page](https://verifymcp.io/servers/pipeworx-io-dol-whd/pipeworx-mcp-dol-whd)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-dol-whd`
- 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-06.

- **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-dol-whd).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 710 tokens (~177/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Dol Whd MCP server?

Dol Whd runs locally as an npm package, launched with npx -y @pipeworx/mcp-dol-whd. 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-dol-whd -- npx -y @pipeworx/mcp-dol-whd
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-dol-whd -- npx -y @pipeworx/mcp-dol-whd
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-dol-whd --command npx --arg -y --arg @pipeworx/mcp-dol-whd
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +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-03 (score 82, +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.

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

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.07 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `whd_search` (~243 tokens)

Search concluded US Department of Labor Wage & Hour Division enforcement cases since FY2005 — wage theft, back wages, minimum wage and overtime violations, child labour, H-1B and H-2A findings. Filter by employer name, NAICS industry code, or state. Returns the employer, industry, violation count, employees due back wages, civil money penalties and the findings dates for each case. Use for "has <employer> been cited for wage violations".

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
- `employer` (string): Employer name, matched as a substring against both the trade name and the legal name.
- `limit` (number): Cases to return, 1-100 (default 20).
- `naics` (string): NAICS industry code as stored by WHD (e.g. "09310").
- `since` (string): Only cases whose findings END on or after this date (YYYY-MM-DD).
- `state` (string): Two-letter state code, e.g. "TX".

### `whd_employer` (~142 tokens)

Full Wage & Hour enforcement history for one employer, with per-case detail and aggregate violation and back-wage figures across every concluded case. Matches the employer against both the registered trade name and the legal name and reports which one hit. Use to answer whether a company is a repeat wage-violation offender.

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
- `employer` (string, required): Employer name, matched against trade name and legal name.
- `limit` (number): Cases to examine, 1-100 (default 100).

### `whd_top_backwages` (~177 tokens)

Rank employers by back wages owed in concluded Wage & Hour enforcement cases, optionally within one NAICS industry or state. Returns cases ordered by the recorded back-wage amount, highest first, with employer, industry and findings dates. Use for "who owes the most back wages in <industry>".

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.
- `limit` (number): Cases to return, 1-100 (default 20).
- `naics` (string): Restrict to one NAICS industry code.
- `since` (string): Only cases whose findings END on or after this date (YYYY-MM-DD).
- `state` (string): Restrict to one two-letter state code.

### `whd_coverage` (~93 tokens)

Report what the Wage & Hour enforcement dataset currently covers: its publication date, update frequency and the findings-date range of the cases returned by a sample query. Use to check how current the enforcement data is before relying on an absence of cases.

Input parameters:

- `_apiKey` (string): Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key.

## Diagnostics

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

## Score history

- 2026-11-06: 83
- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Dol Whd MCP server?

Dol Whd is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dol-whd. DOL Wage & Hour Division, concluded enforcement cases. This page covers its npm package (@pipeworx/mcp-dol-whd).

### Is the Dol Whd MCP server safe to use?

Dol Whd scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 Dol Whd MCP server expose?

Dol Whd exposes 4 tools: whd_search, whd_employer, whd_top_backwages, whd_coverage. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.

### Is the Dol Whd MCP server still maintained?

Dol Whd is still listed as active in the MCP registry. We last reached this channel on 6 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 Dol Whd MCP server under?

Dol Whd 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 Dol Whd MCP server?

VerifyMCP ran 16 checks on Dol Whd, 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-dol-whd
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-dol-whd
- Repository: https://github.com/pipeworx-io/mcp-dol-whd
- Website: https://pipeworx.io/packs/dol-whd
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-dol-whd/pipeworx-mcp-dol-whd.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-dol-whd/pipeworx-mcp-dol-whd/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-dol-whd/pipeworx-mcp-dol-whd.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-dol-whd/pipeworx-mcp-dol-whd