Remote MCP server for searching US WARN Act layoff and plant-closing notices by state, employer, date and location, with dataset description and coverage stats.
What you can do
Describe the WARN Act dataset: coverage, record schema, freshness and gaps, without returning records or needing a key (describe_dataset). Search layoff and plant-closing notices by state, employer, effective date range and county, returning employer, workers impacted, dates, location, layoff type and a provenance key (search_layoff_notices). Check per-state coverage and most recent notice dates to judge freshness before relying on results (layoff_coverage_stats).
When to use it
Useful when tracking mass layoffs or plant closings in the covered states, researching an employer's layoff history, or checking whether the corpus is fresh enough for a given state before citing results.
Requirements
A remote streamable HTTP endpoint; no local install. An API key sent as an Authorization bearer header is needed for search_layoff_notices and layoff_coverage_stats; describe_dataset works without one. Network access required.
Before you install
Paid tools return a payment_required error with a checkout URL, so searches may involve spending money. The API key is passed in the Authorization header and should be kept secret. Coverage is limited to the states listed (CA, TX, NY, IL, NC), so results are not a complete national picture.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.tppflow%2Fwarn-act-layoffs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Takes no parameters.
search_layoff_notices
Search WARN layoff notices
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.
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.
Takes no parameters.
Version history
1
v1.0.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.