Skip to content

AI Layoffs

by ailayoffs.org · remote · no sign-in to list tools · v1.0.0 · published by org.ailayoffs

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

Read only
CompareRegistry entry

4 tools: 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http ai-layoffs https://ailayoffs.org/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Only reads 4Claude Code: allow
  • count_ai_job_lossesAnswers '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,…No findings

    Why it is in this group

    • The name "count_ai_job_losses" says "count": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: How many jobs has AI replaced?
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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).No findings

    Why it is in this group

    • The name "get_ai_layoffs_index" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get the AI Layoffs Index
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_company_ai_layoffsDid a specific company cut jobs because of AI?No findings

    Why it is in this group

    • The name "get_company_ai_layoffs" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Did this company cut jobs because of AI?
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_ai_layoff_eventsSearch the source-cited register of layoffs linked to AI (one row per event, 2023 to date).No findings

    Why it is in this group

    • The name "search_ai_layoff_events" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the AI layoffs register
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ai-layoffs https://ailayoffs.org/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai-layoffs__get_ai_layoffs_index",
      "mcp__ai-layoffs__count_ai_job_losses",
      "mcp__ai-layoffs__search_ai_layoff_events",
      "mcp__ai-layoffs__get_company_ai_layoffs"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as ai-layoffs. Review it before you use it.