# com.tppflow/warn-act-layoffs (remote · mcp.tppflow.com)

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

- Trust score: 72/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `mcp.tppflow.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-tppflow-warn-act-layoffs/mcp.md), [page](https://verifymcp.io/servers/com-tppflow-warn-act-layoffs/mcp)

## Channel facts

- Endpoint: `https://mcp.tppflow.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-27.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 355 tokens (~118/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the com.tppflow/warn-act-layoffs MCP server?

com.tppflow/warn-act-layoffs is a hosted endpoint at https://mcp.tppflow.com/mcp, so there is nothing to install locally. 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 --transport http com-tppflow-warn-act-layoffs 'https://mcp.tppflow.com/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-tppflow-warn-act-layoffs": {
      "type": "http",
      "url": "https://mcp.tppflow.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tppflow-warn-act-layoffs]
url = "https://mcp.tppflow.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tppflow-warn-act-layoffs": {
      "type": "remote",
      "url": "https://mcp.tppflow.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tppflow-warn-act-layoffs --url 'https://mcp.tppflow.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tppflow-warn-act-layoffs:
    url: "https://mcp.tppflow.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tppflow-warn-act-layoffs": {
      "Transport": "http",
      "Url": "https://mcp.tppflow.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tppflow-warn-act-layoffs -t streamable-http -u 'https://mcp.tppflow.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-tppflow-warn-act-layoffs": {
      "type": "http",
      "url": "https://mcp.tppflow.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 72, +1)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `describe_dataset` (~85 tokens)

Describe the WARN 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.

### `search_layoff_notices` (~140 tokens)

Search WARN layoff notices

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 parameters:

- `company`
- `end_date`
- `limit` (integer)
- `location`
- `offset` (integer)
- `start_date`
- `state`

### `layoff_coverage_stats` (~50 tokens)

WARN corpus coverage and freshness

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-tppflow-warn-act-layoffs/mcp#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 63
- 2026-09-03: 63
- 2026-09-02: 62
- 2026-09-01: 62
- 2026-08-31: 61
- 2026-08-30: 61
- 2026-08-29: 60

## Common questions

### What is the com.tppflow/warn-act-layoffs MCP server?

com.tppflow/warn-act-layoffs is an MCP server listed in the public MCP registry as com.tppflow/warn-act-layoffs. Search 5,950 US WARN Act layoff notices by state, employer, and date (CA, TX, NY, IL, NC). This page covers its hosted endpoint (https://mcp.tppflow.com/mcp).

### Is the com.tppflow/warn-act-layoffs MCP server safe to use?

com.tppflow/warn-act-layoffs scores 72 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 com.tppflow/warn-act-layoffs MCP server expose?

com.tppflow/warn-act-layoffs exposes 3 tools: describe_dataset, search_layoff_notices, layoff_coverage_stats. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.

### Does the com.tppflow/warn-act-layoffs MCP server require authentication?

No. We connected to com.tppflow/warn-act-layoffs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.tppflow/warn-act-layoffs MCP server still maintained?

com.tppflow/warn-act-layoffs is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.tppflow.com/mcp
- Website: https://tppflow.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-tppflow-warn-act-layoffs/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tppflow-warn-act-layoffs/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-tppflow-warn-act-layoffs/mcp