warn-act-layoffs
Server Details
Search 5,950 US WARN Act layoff notices by state, employer, and date (CA, TX, NY, IL, NC).
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
Each tool has a distinct role: describe_dataset is metadata-only, layoff_coverage_stats returns per-state counts/freshness, and search_layoff_notices returns records. There is some overlap since describe_dataset also advertises 'how many notices and workers, per-state freshness,' which duplicates layoff_coverage_stats' purpose, but the no-key/with-key split makes the boundary clear enough.
Naming mixes conventions: describe_dataset (verb_noun), layoff_coverage_stats (bare noun phrase with no verb), and search_layoff_notices (verb_noun). All are snake_case and readable, but the pattern isn't predictable — one tool looks like a data getter while behaving like a metadata call.
Three tools is thin for a dataset-access server: there is a metadata call, an aggregate-stats call, and one search call. It is defensible for a narrow API, but a single read/search tool plus one stats tool leaves the surface feeling minimal.
The core lifecycle (discover, assess coverage, search) is covered, but there is no fetch-by-provenance-key/detail endpoint, no pagination or bulk retrieval, and no way to enumerate filter values beyond the stats call. Agents can work around this but will hit dead ends when they need a specific record's full fields.
Available Tools
3 toolsdescribe_datasetDescribe the WARN datasetAInspect
Free, no API key required. Describes the US WARN Act layoff dataset: what a WARN notice is, which states are covered, how many notices and workers, per-state freshness, known coverage gaps, the schema of a record, and how to obtain an API key. Returns no records. Call this before search_layoff_notices to decide whether the data is useful.
Inputs: no named parameters.
layoff_coverage_statsWARN corpus coverage and freshnessAInspect
Per-state coverage of the WARN corpus: how many notices are held for each state and the most recent dates. Use it to check freshness before relying on a search result. Requires an API key.
Inputs: no named parameters.
search_layoff_noticesSearch WARN layoff noticesAInspect
Search US WARN Act mass-layoff and plant-closing notices by state, employer name, effective date range, and county/location. Returns structured records: employer, workers impacted, effective date, notice filing date, location, layoff type, and a provenance key. Useful for layoff tracking, corporate distress and alternative-data signals, employment-law and WARN-compliance research, and recruiting or outplacement leads. Requires an API key.
Inputs: limit, state, offset, company, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search 61,428+ US WARN Act layoff notices: 48 states, 1988-today, daily. Bundle needs no API key.
WARN layoffs, H-1B/LCA visas, SEC 8-K, bankruptcies, DOL claims & JOLTS for all 50 US states.
Search pro jobs with AI exposure and layoff signals, score a résumé, look up WARN layoff notices.
WARN Act layoff notices — state-by-state. Fleet #623.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving WARN Act layoff and plant-closure notices from covered states, filtering by company, state, date, or size, and checking coverage and freshness.70 npmMIT
- AlicenseAqualityBmaintenanceEnables natural-language querying of US WARN Act layoff notices across 48 states since 1988, including searches, employer histories, state totals, and agency revisions, with no API key.61MIT
- AlicenseAqualityCmaintenanceSearch bills and speaker-attributed hearing transcripts across all 50 US state legislatures.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying concluded U.S. Department of Labor Wage & Hour Division enforcement cases, including employer search, case histories, back-wage totals, and dataset coverage.88 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.