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.

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).

Available components

0 this week 72 Trust /100

Last scanned (15 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 355 tokens (~118/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://mcp.tppflow.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tppflow.com CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 7fbe6a9aee88cb5513c1a2f87fd03497
SANs: tppflow.com, *.tppflow.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.tppflow.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
tppflow.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.tppflow.com/mcp Verified 200
http (plaintext) http://mcp.tppflow.com/mcp Inconclusive 406
MCP tools · 3 exposed · ~275 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
describe_dataset ~85

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 present but exposes no named parameters.

No output schema declared.

No examples provided.

layoff_coverage_stats ~50

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 present but exposes no named parameters.

No output schema declared.

No examples provided.

search_layoff_notices ~140

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.

NameTypeReqDescription
company–––
end_date–––
limitinteger––
location–––
offsetinteger––
start_date–––
state–––

No output schema declared.

No examples provided.

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.

remote · mcp.tppflow.com

# add to Claude Code
claude mcp add --transport http com-tppflow-warn-act-layoffs 'https://mcp.tppflow.com/mcp'
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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.tppflow/warn-act-layoffs MCP server?

VerifyMCP ran 11 checks on com.tppflow/warn-act-layoffs, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about com.tppflow/warn-act-layoffs: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.