mcpbeat Sign in

AI Layoffs MCP Server

by ailayoffs Your server? Claim it
not responding

AI Layoffs is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Source-cited register of layoffs linked to AI, plus a live 0-100 AI job-loss index. No key.

Uptime history 42 days of history · worst day 0%
42 days agonow
0.0%
Uptime 24h
0 of 92 checks
4
Tools
read from the server
70 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 September 2026. No other catalogue keeps this.

25 Oct a tool description was rewritten get_company_ai_layoffs
18 Oct a tool description was rewritten get_company_ai_layoffs
8 Oct a tool description was rewritten get_company_ai_layoffs
8 Oct a tool changed the parameters it asks for search_ai_layoff_events
1 Oct 2 tool descriptions were rewritten get_company_ai_layoffs, search_ai_layoff_events
28 Sep a tool description was rewritten search_ai_layoff_events
28 Sep a tool changed the parameters it asks for search_ai_layoff_events

AI Layoffs does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add ai-layoffs --transport http https://ailayoffs.org/mcp
Settings → Connectors → Add custom connector, then paste this address
https://ailayoffs.org/mcp
~/.codex/config.toml
[mcp_servers.ai-layoffs]
url = "https://ailayoffs.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ai-layoffs": {
      "url": "https://ailayoffs.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "ai-layoffs": {
      "type": "http",
      "url": "https://ailayoffs.org/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

company
get_company_ai_layoffs
Did a specific company cut jobs because of AI? Returns the register's verdict for that company (explicit, mixed or blamed: the strongest grade among its cuts), its answer (the strongest position its own words hold: declared, cited, conflicting, attrition, denied, not-named, or statement for a workforce statement with no cut), a plain-language summary, the roles it disclosed vs the roles counted as AI-attributed, and every recorded event with the employer's own words and source. It also lists the company's later cuts that the register checked and left out because neither the employer nor credible press linked them to AI (later_cuts_not_ai_linked, never counted), so a question about the newest layoff is answered either way. Accepts a company name such as 'Klarna' or 'Salesforce'. If the company is not in the register, says so and what that does and does not mean; for a notable layoff the register checked and found not linked to AI, it returns that answer with the employer's own reason and source.
count
count_ai_job_losses
Answers 'how many jobs has AI replaced (or cost) this year?' with the register's published count: roles disclosed in layoffs linked to AI, roles where the employer itself named AI, the evidence-weighted headline figure, and the independent Challenger, Gray & Christmas count of US cuts attributed to AI. Each figure carries its scope (worldwide or US), its period and its definition, plus the ready-made answer sentence. The totals are computed over the whole register, so they are the published figures, not a sum of search results. Takes no arguments.
layoff
search_ai_layoff_events
Search the source-cited register of layoffs linked to AI (one row per event, 2023 to date). Filter by company, free text, attribution, evidence tier, execution status, country, sector, affected role and date range; call with no arguments for the most recent events. Each event returns the employer's own stated reason (claim), roles counted vs reported but not counted, execution status, and a link to its source and its ailayoffs.org company page; set full_context for each event's longer context paragraph.
layoffs
get_ai_layoffs_index
Current 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). Returns the value, its band, the uncertainty range, the change vs last month, the three weighted components with what each reads, the as-of date, and a ready-made citation string. Takes no arguments.

Endpoints

URLTransportStateLatencyChecked
https://ailayoffs.org/mcp streamable-http answering 70 ms 0 min ago

Alternatives to AI Layoffs

same job, measured the same way
A
Agent Rails Index
by workers-penny-mcamp-penny-mcp-rails

Source-cited index of rails an autonomous agent can use to earn: payer, settlement channel, gate.

1 tools answering
AllRatesToday exchange rates (hosted)
by allratestoday

Live FX + official central-bank rates, 110+ sources. Hosted, keyless, nothing to install.

11 tools answering
Jobo Job Search
by jobo

Search a live index of millions of open jobs from employer career sites and 100+ ATS platforms.

54 installs/wk answering
TouchDesigner Atlas
by grigabyte

An atomised index of TouchDesigner plus a live bridge, exposed to AI agents over MCP.

local only
AITeamGuide AI agent prices
by aiteamguide

Read-only lookups of public AI agent pricing, free plans and source links. No API key.

4 tools answering
Fxabsolute
by varsansri

Five years of 1-minute forex, index and crypto candles, plus a live bridge to a trader's chart.

47 installs/wk local only
Company Screening
by tributarydata

UK company register lookups plus US, EU and UN sanctions screening. Every answer cites source.

answering
Registry
by rootz-rental

AI-native Caribbean vacation-rental registry: pricing, licensing, availability, source-linked.

16 tools answering

AI Layoffs — questions

Answers built from our own checks of this server.

What can AI Layoffs do?
It exposes 4 tools, read directly from the server on our last check. Among them: count_ai_job_losses, get_ai_layoffs_index, get_company_ai_layoffs, search_ai_layoff_events. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AI Layoffs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 70 ms. The bar chart above shows every period we have measured.
The registry lists AI Layoffs as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect AI Layoffs?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AI Layoffs need an API key?
No. AI Layoffs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.