mcp-wagewatch
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-wagewatchFind wage theft cases for Tyson Foods in Arkansas"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-wagewatch
MCP server over the U.S. Department of Labor Wage and Hour Division (WHD) enforcement dataset: employer wage-theft history, back wages owed, civil penalties, and affected-employee counts. Built for worker-justice nonprofits, legal-aid intake, and union researchers.
The data is the WHISARD compliance-action dataset (every concluded WHD compliance action since FY2005) served from the DOL Open Data API. This server wraps the raw column names (trade_nm, bw_atp_amt, ee_violtd_cnt, ...) into clean, documented tool outputs.
Tools
Tool | Arguments | Returns |
|
| Enforcement cases matching the employer name, largest back wages first. Per case: employer, location, findings dates, back wages, civil penalties, employees affected, violation count. |
|
| Aggregate totals across matching cases: total back wages, total employees affected, total civil penalties, case count, findings date range. |
|
| Top cases in a state where a violation was found, ordered by back wages. Optional NAICS-prefix industry filter. |
|
| Full record for one case, including the per-statute breakdown (which laws were cited: FLSA, MSPA, H-1B, FMLA, Davis-Bacon, child labor, and so on). |
Related MCP server: DOL WHD MCP
Data source
Base URL:
https://apiprod.dol.gov/v4Query path:
GET /get/WHD/enforcement/json(agencyWHD, endpointenforcement, tableWHD_enforcement)Auth: a free
X-API-KEY, sent only as a request header (never in the query string, so it stays out of URLs and logs).Filtering: the
filter_objectquery parameter takes a JSON string withfield/operator/value(operatorseq,neq,gt,lt,in,not_in,like), composable withand/or. Paging vialimit/offset, ordering viasort_by/sort.Scope: one row per concluded compliance action since FY2005.
Sources:
DOL API User Guide (endpoint template, auth,
filter_objectsyntax): https://www.dataportal.dol.gov/pdf/dol-api-user-guide.pdfLive dataset catalog (agency/endpoint identifiers): https://apiprod.dol.gov/v4/datasets
Dataset landing page: https://catalog.data.gov/dataset/wage-and-hour-division-compliance-action-data
WHISARD column dictionary: https://github.com/jeremybmerrill/whd/blob/master/lib/data/whd_data_dictionary.csv
Field map (WHISARD column to normalized output)
WHISARD column | Normalized field |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sum of statute-level |
|
|
|
Notes:
There is no single total-CMP-dollar column in WHISARD.
cmp_assd_cntis a count of assessments; the dollar penalties live in per-statute columns (flsa_cmp_assd_amt,mspa_cmp_assd_amt,h1b_cmp_assd_amt, and so on).civil_penaltiessums those.back_wages_summaryaggregates client-side (the API does not expose a group-by), over up tomax_casesmatching rows (default 1000). Ifcappedis true the totals are a floor.Name search uses SQL
LIKEontrade_nmandlegal_name, wrapping the term as%term%. The term is uppercased defensively (WHD stores names largely in uppercase) andLIKEmetacharacters (%,_,\) are escaped so they match literally. See the caveats below.
Install
No build step. Runs directly on tsx.
git clone https://github.com/haksanlulz/mcp-wagewatch.git
cd mcp-wagewatch
npm installAPI key
Register for a free DOL Open Data API key at https://dataportal.dol.gov/registration, then expose it as DOL_API_KEY:
export DOL_API_KEY=your-key-here # macOS / Linux
setx DOL_API_KEY your-key-here # Windows (new shells)Without the key the tools return a clear error telling you to set it. The key is never logged.
MCP client config
Point your MCP client at index.ts via tsx. Use an absolute path.
{
"mcpServers": {
"wagewatch": {
"command": "npx",
"args": ["tsx", "/absolute/path/to/mcp-wagewatch/index.ts"],
"env": { "DOL_API_KEY": "your-key-here" }
}
}
}Example
Call employer_violations with { "employer": "tyson", "state": "AR", "limit": 1 }:
{
"query": { "employer": "tyson", "state": "AR" },
"count": 1,
"cases": [
{
"case_id": "1234567",
"employer": "TYSON FOODS INC",
"legal_name": "TYSON FOODS INCORPORATED",
"location": { "street": "2200 DON TYSON PKWY", "city": "SPRINGDALE", "state": "AR", "zip": "72762" },
"naics_code": "311615",
"naics_description": "Poultry Processing",
"findings_start_date": "2021-01-01",
"findings_end_date": "2022-01-01",
"back_wages": 150000.5,
"civil_penalties": 7500,
"employees_affected": 88,
"violations": 12
}
]
}Then pass a case_id to case_detail for the per-statute breakdown.
Caveats
The metadata endpoint is key-gated and this was built without a key, so:
The column names are checked against the published WHISARD data dictionary (table
whd_whisard) and the dataset description, not against the liveWHD/enforcementmetadata endpoint (which requires the key). The v4enforcementendpoint is the same underlying WHISARD data, so the names are expected to match, but the exact live field list is unconfirmed. The normalizer is defensive: unknown-shaped values coerce tonullrather than throwing, and the CMP total scans every*_cmp_assd_amtcolumn present.LIKEcase-sensitivity on the DOL endpoint is unconfirmed, so the search term is uppercased defensively before the%term%wrap (WHD stores names largely in uppercase) andLIKEmetacharacters are escaped to match literally. If name searches still under-return, casing on the endpoint is the place to look.Run
npm run smokewith a real key to confirm field names and behavior end to end before relying on output.
Develop
npm test # vitest, fetch mocked with the documented response shapes (no key needed)
npm run smoke # one live call per tool (needs DOL_API_KEY; skips cleanly without)
npm run typecheckLicense
MIT. See LICENSE. Public U.S. government data from the U.S. Department of Labor. Unofficial, not affiliated with DOL.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/haksanlulz/mcp-wagewatch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server