# Warn Notices (npm · @pipeworx/mcp-warn-notices) WARN Act layoff notices — state-by-state. Fleet #623. - Trust score: 80/100 (high trust) - Change this week: 0 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-warn-notices/warn-notices-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-warn-notices/warn-notices-mcp) - npm · `@pipeworx/mcp-warn-notices`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices.md), [page](https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-warn-notices` - Version: `0.2.0` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-warn-notices). - Clear OSI-approved license (MIT). - Actively maintained (last published 6 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 71/100 - AI-judged instruction clarity (excellent). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **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. ## Install ### 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. ### Claude ```bash claude mcp add pipeworx-io-warn-notices -- npx -y @pipeworx/mcp-warn-notices ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-warn-notices": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-warn-notices" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-warn-notices": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-warn-notices" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-warn-notices -- npx -y @pipeworx/mcp-warn-notices ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-warn-notices": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-warn-notices" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-warn-notices --command npx --arg -y --arg @pipeworx/mcp-warn-notices ``` ### Hermes ```yaml mcp_servers: pipeworx-io-warn-notices: command: "npx" args: ["-y", "@pipeworx/mcp-warn-notices"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-warn-notices": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-warn-notices" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-warn-notices -t stdio -c npx -a -y @pipeworx/mcp-warn-notices ``` ### Other ```json { "mcpServers": { "pipeworx-io-warn-notices": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-warn-notices" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-29 (score 80) First indexed and scored. ## MCP tools (4) ### `warn_search` (~228 tokens) 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. Input parameters: - `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. ### `warn_recent` (~167 tokens) 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. Input parameters: - `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. ### `warn_company` (~127 tokens) 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. Input parameters: - `company` (string, required): Employer name, free text — "Tesla" matches "Tesla, Inc." and "TESLA MOTORS". - `limit` (number): Max notices to return (default 200, max 500). ### `warn_coverage` (~81 tokens) 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. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices#diagnostics ## Score history - 2026-11-05: 80 - 2026-11-04: 80 - 2026-11-03: 80 - 2026-11-02: 80 - 2026-11-01: 80 - 2026-10-31: 80 - 2026-10-30: 80 - 2026-10-29: 80 ## Common questions ### 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. ### What did VerifyMCP test on the Warn Notices MCP server? VerifyMCP ran 15 checks on Warn Notices, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Warn Notices: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-warn-notices - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-warn-notices - Repository: https://github.com/pipeworx-io/mcp-warn-notices - Website: https://pipeworx.io/packs/warn-notices - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-warn-notices/pipeworx-mcp-warn-notices