Data Collection
tppflow.com
Provides search and analysis tools for US WARN Act layoff notices, including dataset descriptions and coverage statistics.
ENDPOINT 1
https://mcp.tppflow.com/mcp
MCP server metadata
- Name
- teos-warn
- Version
- 1.0.0
Query normalized US WARN Act layoff and closure notices -- employer, location, workers impacted, effective date and filing date -- across California, Texas, New York, Illinois and North Carolina. Call describe_dataset first (free, no key) to see coverage, freshness and known gaps. The data tools require an API key; without one they return a payment_required error carrying a checkout URL.
Known tools 3
search_layoff_noticesSearch US WARN Act mass-layoff and plant-closing notices by state, employer name, effective date range, and county/location.
Inferred read-onlylayoff_coverage_statsPer-state coverage of the WARN corpus: how many notices are held for each state and the most recent dates.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.teos-warn]
url = "https://mcp.tppflow.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"teos-warn": {
"type": "http",
"url": "https://mcp.tppflow.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: teos-warn
Remote MCP URL: https://mcp.tppflow.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"teos-warn": {
"url": "https://mcp.tppflow.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"teos-warn": {
"type": "http",
"url": "https://mcp.tppflow.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "teos-warn",
"transport": "streamable-http",
"url": "https://mcp.tppflow.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.