warn-act-layoffs

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

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
39%
Naming quality
87%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~450Tokens (tool definitions)
~781 BTypical response size
Minimal attention impact (0.35% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "warn-act-layoffs": {
      "url": "https://mcp.tppflow.com/mcp"
    }
  }
}

Remote endpoints

https://mcp.tppflow.com/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢describe_dataset

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "describe_datasetArguments"
}
🟢search_layoff_notices(state, company, start_date, end_date, location, ...)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "state": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "State"
    },
    "company": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Company"
    },
    "start_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Start Date"
    },
    "end_date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "End Date"
    },
    "location": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Location"
    },
    "limit": {
      "default": 100,
      "title": "Limit",
      "type": "integer"
    },
    "offset": {
      "default": 0,
      "title": "Offset",
      "type": "integer"
    }
  },
  "title": "search_layoff_noticesArguments"
}
🟢layoff_coverage_stats

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "layoff_coverage_statsArguments"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools
verifiedversion not recorded3 tools