Analytics
ailayoffs.org
Provides an index, counts, and searchable register of AI-attributed layoffs and company-level AI job cuts.
ENDPOINT 1
https://ailayoffs.org/mcp
MCP server metadata
- Name
- ai-layoffs
- Version
- 1.0.0
AI Layoffs publishes an open, source-cited register of layoffs linked to AI (2023 to date) and a live 0-100 index of AI job-loss pressure. All tools are read-only and free to use. Which tool answers which question: the current reading or trend -> get_ai_layoffs_index; 'how many jobs has AI replaced' -> count_ai_job_losses; one company -> get_company_ai_layoffs; lists, filters and recent events -> search_ai_layoff_events. How to read the fields: attribution (who tied the cut to AI). explicit: The company itself declared the layoff AI-related. blamed: A credible source named AI, but the company did not. Shown as context and never counted: prong 1 of our standard requires the employer's own source to name AI, so a blamed event is a failed claim, not a discounted one. mixed: AI was cited alongside other material factors (cost, demand). evidence_tier (how strong the source is). tier1 (Primary-source attributed): AI named as a workforce driver in the company's own SEC filing, on-record earnings call, or official statement, with the event corroborated by a structured source. tier2 (Reputable-press attributed): AI named as a cause by credible journalism quoting a named company source, but not yet in a company filing. tier3 (Inferred / single-source): Attribution from one secondary tracker, an unnamed source, or vague forward-looking language. execution (did it happen). executed: The reduction has been carried out. partial: Some of the cut is done, the rest pending. announced: A stated plan, not yet carried out (often multi-year). unknown: Execution status not established. reversed: The cut was rolled back or rehired against (e.g. Commonwealth Bank). roles_counted vs roles_reported_not_counted: counted roles meet the register's AI-attribution standard and enter the totals; reported roles were disclosed by the employer but are not counted, because the employer did not attribute them to AI or did not state a qualifying figure. Reading results correctly: every figure carries its scope (worldwide or US) and its period; an announced plan is not a completed cut (see execution); each event links its primary source (source.url) and its page on the site (page_url); get_ai_layoffs_index returns the citation string for the index. A company absent from the register has no recorded AI-linked event, which is not evidence that it made no layoffs.
Known tools 4
get_ai_layoffs_indexCurrent reading of the AI Layoffs Index, a 0-100 score of AI-attributed job-loss pressure scaled against AI's own history since 2023 (not a share of all jobs).
Inferred read-onlysearch_ai_layoff_eventsSearch the source-cited register of layoffs linked to AI (one row per event, 2023 to date).
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.ai-layoffs]
url = "https://ailayoffs.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ai-layoffs": {
"type": "http",
"url": "https://ailayoffs.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ai-layoffs
Remote MCP URL: https://ailayoffs.org/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": {
"ai-layoffs": {
"url": "https://ailayoffs.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ai-layoffs": {
"type": "http",
"url": "https://ailayoffs.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ai-layoffs",
"transport": "streamable-http",
"url": "https://ailayoffs.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for ailayoffs.org was fetched 2026-10-01T23:15:22.328Z.
ailayoffs.org is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.