Warn Notices
NPM · @PIPEWORX/MCP-WARN-NOTICES · 2 COMPONENTS
WARN Act layoff notices — state-by-state. Fleet #623.
Available components
Last scanned (8 hours ago)
Scores higher than 65% of npm servers
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-warn-notices). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 658 tokens (~164/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-warn-notices@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-warn-notices |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-warn-notices/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561007444 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:602859cd955f56090abb6be860a51e634063cd7ec27af3ed88b82de2201b28661bdb17ca60bd6614b74715924db615053715b6bad87f85dc61a83d45e |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
warn_company ~127
Every WARN Act layoff and closure notice one employer has filed, across all covered states, with a per-state and per-year breakdown. Answers "has Tesla filed layoff notices", "how many workers has Amazon laid off by WARN filing", "which sites did this company close". Use to trace one employer's layoff history rather than browsing a date range.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Employer name, free text — "Tesla" matches "Tesla, Inc." and "TESLA MOTORS". |
| limit | number | – | Max notices to return (default 200, max 500). |
No output schema declared.
No examples provided.
warn_coverage ~81
Which US states WARN layoff-notice coverage extends to, how many notices are available for each, and the date of the newest notice per state. Answers "which states do you have WARN data for", "how current is the layoff data", "is Georgia covered". Read this before treating an empty WARN search result as evidence that no layoffs were filed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
warn_recent ~167
Most recent US WARN Act layoff and plant-closure notices across every covered state, newest first — the earliest public signal that an employer is cutting jobs, filed roughly 60 days before the layoff takes effect. Answers "recent layoff notices", "who announced layoffs this month", "latest WARN filings in Texas". Returns employer, site, worker count and effective date, plus states_covered so a quiet month is distinguishable from a coverage gap.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look back this many days from today by WARN notice date (default 30). |
| limit | number | – | Max notices to return (default 50, max 500). |
| state | string | – | Two-letter state code to restrict to, e.g. "NY". Omit for all covered states. |
No output schema declared.
No examples provided.
warn_search ~228
Search US WARN Act layoff and plant-closure notices filed with state labor departments — the legally required 60-day advance notice of a mass layoff or site closure. Returns employer name, site city and county, notice date, layoff effective date, number of workers affected, and whether the filing is a layoff or a closure. Answers "which employers filed layoff notices in Texas this year", "layoff filings above 200 workers since June", "WARN notices in Suffolk County". Covers the states named in states_covered on every response.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Employer name, free text. Matched loosely against the filed legal name, so "Tesla" finds "Tesla, Inc.". |
| limit | number | – | Max notices to return (default 50, max 500). |
| min_employees | number | – | Only notices affecting at least this many workers. |
| since | string | – | Earliest WARN notice date, YYYY-MM-DD. |
| state | string | – | Two-letter state code, e.g. "TX". Omit to search every covered state. |
No output schema declared.
No examples provided.
How do I install the Warn Notices MCP server?
Warn Notices runs locally as an npm package, launched with npx -y @pipeworx/mcp-warn-notices. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-warn-notices
claude mcp add pipeworx-io-warn-notices -- npx -y @pipeworx/mcp-warn-notices
What is the Warn Notices MCP server?
Warn Notices is an MCP server listed in the public MCP registry as io.github.pipeworx-io/warn-notices. WARN Act layoff notices, state-by-state. Fleet #623. This page covers its npm package (@pipeworx/mcp-warn-notices).
Is the Warn Notices MCP server safe to use?
Warn Notices scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Warn Notices MCP server expose?
Warn Notices exposes 4 tools: warn_search, warn_recent, warn_company, warn_coverage. Their descriptions and schemas cost roughly 603 tokens of context every time the server is loaded.
Is the Warn Notices MCP server still maintained?
Warn Notices is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Warn Notices MCP server under?
Warn Notices declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.