warn-mcp
This MCP server provides six tools for querying US WARN Act layoff data (1988–today) and tracking agency revisions, all read-only and keyless.
Search layoff notices – Filter by employer, state, date range, minimum headcount; get counts, totals, and newest matches.
Latest layoff notices – Rolling ~14-day feed of newly published notices, optionally by state.
Employer layoff history – Full record for one employer: notices, workers, states, first/latest activity.
State layoff totals – National leaderboard by state or month-by-month series for one state.
Agency revisions – Field-level diff of daily dataset builds: amended fields, withdrawn/returned notices, cause classification.
Dataset status – Last rebuild time, stale states, license, raw endpoints for attribution.
Click on "Deploy 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., "@warn-mcp Has Starbucks filed any WARN notices this year, and in which states?"
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.
warn-mcp — US layoff data (WARN Act) as an MCP server
61,428 mass-layoff notices · 48 states · 1988 → today · rebuilt every morning · no API key · zero dependencies.
Every US state publishes the layoff notices employers must file under the WARN Act, and every state publishes them differently — a web page here, a pile of PDFs there, a search form somewhere else. WARN Feed scrapes all 48 of them daily and normalizes them into one schema. This is that dataset wired into the Model Context Protocol, so Claude, Cursor, Continue or your own agent can ask questions like:
"Has Starbucks filed any WARN notices this year, and in which states?" "What layoffs were announced in the last two weeks in Texas?" "Which state had the most workers affected in 2026?" "Did any agency quietly change or delete a notice this week?"
Install
Nothing to build and nothing to install into your Python environment — the server is standard library only.
Claude Desktop — one file, no terminal: download
warn-mcp.mcpb
and drag it onto Claude Desktop's Settings → Extensions window. That bundle is
this repo's server plus a manifest; it needs a python3 on your PATH and
nothing else. The same file is listed as the installable package for
io.github.APProj/warn-mcp in the
MCP registry.
Claude Desktop / Claude Code / anything that reads an mcpServers block:
{
"mcpServers": {
"warn": {
"command": "uvx",
"args": ["--from", "git+https://github.com/APVentureEngine/warn-mcp", "warn-mcp"]
}
}
}Claude Code, one line:
claude mcp add warn -- uvx --from git+https://github.com/APVentureEngine/warn-mcp warn-mcpNo uv? Clone and run it with plain Python:
git clone https://github.com/APVentureEngine/warn-mcp && cd warn-mcp
python3 -m warn_mcp.server --selftest # exercises every tool against live data{
"mcpServers": {
"warn": { "command": "python3", "args": ["-m", "warn_mcp.server"], "cwd": "/path/to/warn-mcp" }
}
}Related MCP server: treasury-fiscaldata-mcp
Hosted: a URL, no install (ChatGPT / Claude.ai connectors, n8n, any remote client)
If your client wants a remote MCP server rather than a subprocess, point it at:
https://mQpACuIiQcnwK93JY.apify.actor/mcp (Streamable HTTP)Same six tools, same daily-rebuilt data, same code as this repo. One honest
caveat: the host (Apify) requires the caller's own API token, because it
meters the compute to the account that calls it. Create a free Apify account,
copy your token, and send it as Authorization: Bearer <your-apify-token>.
We charge nothing, we see nothing, and we store nothing about your queries.
If your client supports stdio, the .mcpb bundle above needs no token at all
and is the better route.
claude mcp add --transport http warn https://mQpACuIiQcnwK93JY.apify.actor/mcp \
--header "Authorization: Bearer <your-apify-token>"This endpoint is also listed as the remotes entry for
io.github.APProj/warn-mcp in the
official MCP registry.
Or run it over HTTP (Streamable HTTP transport)
The same six tools, same implementation, spoken over MCP's Streamable HTTP transport instead of stdio — for clients that want a URL rather than a subprocess, and for putting one shared instance behind your own team:
docker build -t warn-mcp . && docker run -p 8080:8080 warn-mcp
# -> http://localhost:8080/mcp (and a short human page at http://localhost:8080/)
claude mcp add --transport http warn http://localhost:8080/mcpNo Docker? python3 http/app.py does the same thing — it is standard library
only, like everything else here. PORT selects the port, /healthz returns
{"ok":true}, and the server is stateless, so you can run as many replicas as
you like behind any load balancer.
It is deliberately keyless: the data underneath is public and read-only, the server keeps no session state and stores nothing about callers. Do not bolt auth onto a public deployment of it and then advertise it as this server.
Tools
Tool | What it answers |
| Employer / state / date-range / minimum-headcount search across the whole archive. Returns matched notice count, total workers affected, and the newest matches. |
| The rolling ~14-day feed of newly published notices, newest first, optionally one state. |
| One employer's whole WARN record back to 1988 — notices, workers affected, every state it filed in, first and latest activity. |
| Monthly notice counts and workers affected: a national leaderboard by state, or one state's month-by-month series. |
| The dataset's own change log: a field-level diff of consecutive daily builds — |
| Last rebuild time, states flagged stale, license, and the raw endpoints — call it before quoting a number. |
Every answer carries as_of and source, because a layoff figure with no date
and no attribution is not worth repeating. Where the data is weaker than it
looks, the tool says so in a caveat field rather than letting the model round
it off: headcount is only counted where the agency published one, employer names
are normalized by an auditable rule table rather than a corporate-registry join,
and row_absent in the revision log means the agency stopped publishing a
notice — not that the layoff was cancelled.
Why an MCP server and not just the CSV
The CSV is right there and it is free — take it. This exists for the case where a model needs one specific answer out of a 9 MB file: the tools do the filtering and the arithmetic locally, so an agent spends a few hundred tokens instead of a context window, and it gets the freshness stamp with the answer.
agency_revisions is the part you cannot reconstruct from any single copy of
the data. A state agency editing its own WARN page leaves no changelog, so a
mirror taken today simply is today's truth. WARN Feed diffs yesterday's
build against today's and keeps the field-level log — 638 logged changes
since 2026-08-31, including 274 notices that stopped appearing. One honest
caveat, stated in every response: a logged change can come from the agency
amending or withdrawing a notice or from an improvement to this project's
parser, and the log does not guess which — cause_class labels only what is
mechanically distinguishable (field_populated, field_cleared,
format_only, value_changed, unknown).
Caching and network
Tools read the free public WARN Feed endpoints over HTTPS and cache them on disk
(~/.cache/warn-mcp, override with WARN_MCP_CACHE) with ETag revalidation, so
ten tool calls in a row make at most one request per file per hour
(WARN_MCP_TTL, seconds). If the network is down and a cached copy exists, the
cached copy is served and its own as_of tells you how old it is.
There is no key, no signup, no rate limit and no telemetry — this server sends nothing anywhere except plain GETs for public files.
Data, license, attribution
Data is compiled from official state WARN publications and released under
CC BY 4.0 — credit "WARN Feed" and link back. This server's code is MIT.
Not affiliated with any state agency or the US Department of Labor; state
agencies' own postings are the authority and are occasionally revised (see
agency_revisions).
Dataset repo: https://github.com/APVentureEngine/warn-act-notices
Raw HTTP API and per-state files: https://approjects-warn-act-notices.static.hf.space/api.html
Hugging Face: https://huggingface.co/datasets/APProjects/us-warn-act-layoffs-notices-daily
The one paid thing
Everything above is free and stays free. If you need to be told — your own list of employers matched against every daily refresh and pushed to a private alert page, a calendar feed, or a private RSS feed you point Slack, Discord or Teams at — that is WARN Watch, $49/year, with a free 30-day trial and no card. It is the only thing here that costs money.
Bugs, a state we should cover, a tool you want: open an issue.
Available Tools
6 toolsagency_revisionsAInspect
Change log of the dataset itself: what differed between consecutive daily builds of the WARN notice table, since 2026-08-31. Each change is one of 'amended' (a tracked field of an existing notice changed — employees_affected, effective_date, location, notice_type, company, notice_date), 'row_absent' (a notice stopped appearing) or 'row_returned' (an absent notice came back). A change can come from the state agency amending or withdrawing a notice OR from an improvement to this project's parser; the log records the observation, never the cause, and cause_class labels only what is mechanically distinguishable (field_populated, field_cleared, format_only, value_changed, unknown). Filters combine with AND. Returns matched_changes, by_change_type, by_cause_class, log_covers_from/to, and up to limit changes newest observed_date first, each with id, state, company, notice_date, change_type, cause_class, field, old_value, new_value. Not a search for notices: use search_layoff_notices for notices and employer_layoff_history for one employer's full record.
Inputs: limit, since, state, company, +1 more.
dataset_statusAInspect
Freshness and coverage of the dataset itself: when it was last rebuilt, which states are flagged stale, the license, and the raw endpoints. Call this before quoting a number so you can attribute it correctly.
Inputs: no named parameters.
employer_layoff_historyAInspect
Every WARN notice one employer has filed, in any covered state, back to 1988: notice count, total workers affected, states, first and latest activity. Returns employers_matched, employers (up to 10 distinct canonical names, most workers affected first) and notices_for_best_match (up to limit notices of the top employer, newest notice_date first). For a date- or state-bounded question use search_layoff_notices.
Inputs: company (required), limit.
latest_layoff_noticesAInspect
The rolling feed of newly published WARN notices (the last ~14 days as the agencies posted them), newest notice_date first, optionally one state. Use this for 'what layoffs were announced recently'. Returns count_in_window plus up to limit notices in the same row shape as search_layoff_notices; for older dates or an employer filter use search_layoff_notices instead.
Inputs: limit, state.
search_layoff_noticesAInspect
Search US WARN Act mass-layoff notices across 48 states, 1988 to today, by employer name, state, date range and minimum headcount (filters combine with AND; at least one is required). Returns matched_notices, matched_workers_affected and up to limit notices, newest notice_date first, each with id, state, company, location, employees_affected, notice_date, effective_date, notice_type and first_seen. Read-only, no key. For only the newest ~14 days use latest_layoff_notices; for one employer's whole record use employer_layoff_history.
Inputs: limit, since, state, until, +2 more.
state_layoff_totalsAInspect
Monthly WARN notice counts and workers affected. With no state, returns a national leaderboard by state in series (grouped_by=state, most workers affected first); with a state, the month-by-month series for it (grouped_by=month, oldest first). Optionally restrict to one four-digit year. totals carries overall notices and workers for the selection; notices without a published headcount count 0 workers. Aggregates only — use search_layoff_notices for the notices.
Inputs: year, state.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool occupies a clearly distinct niche: general search, recent feed, employer history, state aggregates, dataset freshness, and change log. The descriptions explicitly cross-reference the other tools, so an agent can reliably pick the right one without ambiguity.
All names use lowercase snake_case and follow a recognizable subject-prefix structure like search_, latest_, employer_, and state_. The only minor deviation is that search_layoff_notices is verb-led while most other names are noun phrases, but the pattern is still predictable.
Six tools is well-scoped for a specialized WARN dataset server. Each tool earns its place by covering a distinct query mode or operational need, with no obvious redundancy or bloat.
The read-only domain is well covered: filtered search, recent notices, employer history, state totals, dataset status, and revision tracking are all present. Minor gaps exist, such as no direct lookup by notice id and no explicit pagination beyond `limit`, but agents can usually work around these with the available search and history tools.
Maintenance
Related MCP Connectors
Search 5,950 US WARN Act layoff notices by state, employer, and date (CA, TX, NY, IL, NC).
Search pro jobs with AI exposure and layoff signals, score a résumé, look up WARN layoff notices.
WARN layoffs, H-1B/LCA visas, SEC 8-K, bankruptcies, DOL claims & JOLTS for all 50 US states.
Apify MCP: retrainmap/warn-notices - WARN layoff notices CA/IL/NY, normalised from agency files
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables users to query U.S. labor statistics, including employment, CPI, and wages, directly from the Bureau of Labor Statistics Public Data API. It provides tools to retrieve real-time economic time series data, browse popular series, and access survey metadata through natural language.61MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying U.S. Treasury fiscal data including debt, interest rates, auctions, and more via natural language, with no API key required.MIT
- AlicenseNot gradedqualityFmaintenanceProvides access to US Treasury Fiscal Data via a free, no-auth public API. Enables querying government financial data through natural language.MIT
- AlicenseAqualityBmaintenanceAn MCP server for SEC EDGAR written in Rust: company filings, full-text search, XBRL financials, insider transactions and company info. A single native binary; no API key.3214MIT