Skip to main content
Glama

warn-act-layoffs

Server Details

Search 5,950 US WARN Act layoff notices by state, employer, and date (CA, TX, NY, IL, NC).

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation4/5

Each tool has a distinct role: describe_dataset is metadata-only, layoff_coverage_stats returns per-state counts/freshness, and search_layoff_notices returns records. There is some overlap since describe_dataset also advertises 'how many notices and workers, per-state freshness,' which duplicates layoff_coverage_stats' purpose, but the no-key/with-key split makes the boundary clear enough.

Naming Consistency3/5

Naming mixes conventions: describe_dataset (verb_noun), layoff_coverage_stats (bare noun phrase with no verb), and search_layoff_notices (verb_noun). All are snake_case and readable, but the pattern isn't predictable — one tool looks like a data getter while behaving like a metadata call.

Tool Count3/5

Three tools is thin for a dataset-access server: there is a metadata call, an aggregate-stats call, and one search call. It is defensible for a narrow API, but a single read/search tool plus one stats tool leaves the surface feeling minimal.

Completeness3/5

The core lifecycle (discover, assess coverage, search) is covered, but there is no fetch-by-provenance-key/detail endpoint, no pagination or bulk retrieval, and no way to enumerate filter values beyond the stats call. Agents can work around this but will hit dead ends when they need a specific record's full fields.

Available Tools

3 tools
describe_datasetDescribe the WARN datasetAInspect

Free, no API key required. Describes the US WARN Act layoff dataset: what a WARN notice is, which states are covered, how many notices and workers, per-state freshness, known coverage gaps, the schema of a record, and how to obtain an API key. Returns no records. Call this before search_layoff_notices to decide whether the data is useful.

Inputs: no named parameters.

layoff_coverage_statsWARN corpus coverage and freshnessAInspect

Per-state coverage of the WARN corpus: how many notices are held for each state and the most recent dates. Use it to check freshness before relying on a search result. Requires an API key.

Inputs: no named parameters.

search_layoff_noticesSearch WARN layoff noticesAInspect

Search US WARN Act mass-layoff and plant-closing notices by state, employer name, effective date range, and county/location. Returns structured records: employer, workers impacted, effective date, notice filing date, location, layoff type, and a provenance key. Useful for layoff tracking, corporate distress and alternative-data signals, employment-law and WARN-compliance research, and recruiting or outplacement leads. Requires an API key.

Inputs: limit, state, offset, company, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving WARN Act layoff and plant-closure notices from covered states, filtering by company, state, date, or size, and checking coverage and freshness.
      70 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables natural-language querying of US WARN Act layoff notices across 48 states since 1988, including searches, employer histories, state totals, and agency revisions, with no API key.
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying concluded U.S. Department of Labor Wage & Hour Division enforcement cases, including employer search, case histories, back-wage totals, and dataset coverage.
      88 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources