Dol Whd
NPM · @PIPEWORX/MCP-DOL-WHD · 2 COMPONENTS
DOL Wage & Hour Division — concluded enforcement cases
Available components
Last scanned (7 hours ago)
Scores higher than 75% of npm servers
Category Finance and Payments
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-dol-whd). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +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.
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-dol-whd@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-dol-whd |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-dol-whd/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617561625 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4adbb8ccae352194603df6789391de7b6b57f2a087a2ea5484ce4e984069e620e73ea6a12dce6b4939e9499093dfa14e99fba9544ac44cfdb2d069b85 |
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 →
whd_coverage ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key. |
No output schema declared.
No examples provided.
whd_employer ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional. Your own free DOL Open Data Portal key (dataportal.dol.gov); omit it to use the platform key. |
| employer | string | yes | Employer name, matched against trade name and legal name. |
| limit | number | – | Cases to examine, 1-100 (default 100). |
No output schema declared.
No examples provided.
whd_search ~243
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".
| Name | Type | Req | Description |
|---|---|---|---|
| _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". |
No output schema declared.
No examples provided.
whd_top_backwages ~177
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>".
| Name | Type | Req | Description |
|---|---|---|---|
| _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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-dol-whd
claude mcp add pipeworx-io-dol-whd -- npx -y @pipeworx/mcp-dol-whd
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.