Warn Notices MCP server

warn-notices

US WARN Act layoff and plant-closure notices — the 60-day advance filings employers must make before a mass layoff — from state labor departments.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Coverage is partial on purpose, and every response says so. There is no national WARN database: the federal DOL neither collects nor publishes one, so employers file with the state where the site sits and each state publishes on its own terms. This pack covers the states that publish machine-readable data and reports exactly which those are.

Tools

Every response carries statescovered. An empty result distinguishes statenotcovered from nomatching_notices, because "Georgia isn't covered" and "this employer filed nothing" are different answers and only one of them is about the employer.

Coverage

Each state is registered in datafreshness separately** (warn-ca, warn-il, …) so one stalled feed is visible instead of being hidden behind a fresher state's date.

Probed and not shipped

Recorded so nobody re-probes them:

rows (company names landing in the date column). Needs row-level repair.

• NJ — XLSX exists, but the state's own file is column-shifted on many

accordion, WA an ASP.NET GridView needing __VIEWSTATE postbacks past page one, FL a paginated table. All scrapeable; none machine-readable.

• PA / WA / FL — real and current, but HTML only. PA is a nested

but stops in 2013, and the modern site is an employer submission form with no public index.

• GA — no current public listing exists. The legacy search still answers

Data sources

• California EDD —
• Illinois WorkNet —
• New York DOL —
• Ohio ODJFS — (annual warn-notice.csv asset)
• Texas Workforce Commission —

Ingest lives in workers/data-pipeline/src/datasets/warn.ts; the per-source traps are documented there. Table: warn_notices (migration 108).

Gotchas worth knowing

than guessed — an invented "Layoff" would read as reported fact.

• Texas publishes no layoff-vs-closure flag. type is null for TX rather

2026-08-29. That is normal for this feed.

• Texas lags. Its newest notice trailed the other states by ~2 months as of

the word "various", so effectivedate is set only when it parses and effectivedateaspublished always carries what was actually written.

• Effective dates are not always dates. Several states publish a range or

so "Tesla" finds "Tesla, Inc."; matchedfilednames echoes back the exact strings matched so a caller can spot a loose match across sister entities.

• Company names are free text. Search matches on a suffix-stripped form,

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "warn-notices": {
      "url": "https://gateway.pipeworx.io/warn-notices/mcp"
    }
  }
}

Shortened. The full README is on GitHub.