Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.APProj/warn-mcp

MCPB · WARN-MCP.MCPB · 2 COMPONENTS · SCANNED OCT 2

Search 61,428+ US WARN Act layoff notices: 48 states, 1988-today, daily. Bundle needs no API key.

+4 this week 43 Trust /100
Trust breakdown (7 categories)

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1282 tokens (~213/item across 6 items; 6 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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.

Install

How do I install the io.github.APProj/warn-mcp server?

io.github.APProj/warn-mcp ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

mcpb · warn-mcp.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

Changelog

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.

  • 2 Oct 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 43

    First indexed and scored.

Diagnostics

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 2 Oct 2026 · Analysed mcpb/https://github.com/APVentureEngine/warn-mcp/releases/download/v0.2.6/warn-mcp.mcpb@0.2.6

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~1,238 tokens

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 →

Tool Tokens
agency_revisions ~432

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.

NameTypeReqDescription
change_typestring–Exactly one of 'amended', 'row_absent', 'row_returned'. Omit for all three.
companystring–Employer name, matched on WHOLE WORDS (case-insensitive), e.g. 'united airlines'. Every word you give must appear as a complete word in the filed name, so 'ford' will NOT return 'Stanford Health Care…
limitinteger–Max changes returned, 1-200 (default 25). matched_changes always reports the full count.
sincestring–Earliest observed_date (the build date on which the change was seen), YYYY-MM-DD. The log starts 2026-08-31; earlier dates return everything.
statestring–Two-letter state code, e.g. 'CA'.

No output schema declared.

No examples provided.

dataset_status ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

employer_layoff_history ~197

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.

NameTypeReqDescription
companystringyesEmployer name, matched on WHOLE WORDS (case-insensitive), e.g. 'united airlines'. Every word you give must appear as a complete word in the filed name, so 'ford' will NOT return 'Stanford Health Care…
limitinteger–Max individual notices returned, 1-200 (default 25).

No output schema declared.

No examples provided.

latest_layoff_notices ~124

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.

NameTypeReqDescription
limitinteger–Max notices returned, 1-200 (default 25).
statestring–Two-letter state code to filter to.

No output schema declared.

No examples provided.

search_layoff_notices ~290

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.

NameTypeReqDescription
companystring–Employer name, matched on WHOLE WORDS (case-insensitive), e.g. 'united airlines'. Every word you give must appear as a complete word in the filed name, so 'ford' will NOT return 'Stanford Health Care…
limitinteger–Max notices returned, 1-200 (default 25).
min_employeesinteger–Only notices affecting at least this many workers.
sincestring–Earliest notice_date, YYYY-MM-DD.
statestring–Two-letter state code, e.g. 'CA'.
untilstring–Latest notice_date, YYYY-MM-DD.

No output schema declared.

No examples provided.

state_layoff_totals ~145

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.

NameTypeReqDescription
statestring–Two-letter state code.
yearstring–Four-digit year, e.g. '2026'.

No output schema declared.

No examples provided.

Common questions

What is the io.github.APProj/warn-mcp server?

io.github.APProj/warn-mcp is listed in the public MCP registry as io.github.APProj/warn-mcp. Search 61,428+ US WARN Act layoff notices: 48 states, 1988-today, daily. Bundle needs no API key. This page covers its MCPB bundle (https://github.com/APVentureEngine/warn-mcp/releases/download/v0.2.6/warn-mcp.mcpb).

Is the io.github.APProj/warn-mcp server safe to use?

io.github.APProj/warn-mcp scores 43 out of 100 on VerifyMCP. 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 io.github.APProj/warn-mcp server expose?

io.github.APProj/warn-mcp exposes 6 tools: search_layoff_notices, latest_layoff_notices, employer_layoff_history, state_layoff_totals, agency_revisions, dataset_status. Their descriptions and schemas cost roughly 1,238 tokens of context every time the server is loaded.

What licence is the io.github.APProj/warn-mcp server under?

io.github.APProj/warn-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.