# AI Layoffs (remote · ailayoffs.org)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `ailayoffs.org`: 72/100 (this document), [markdown](https://verifymcp.io/servers/org-ailayoffs-ai-layoffs/ailayoffs.md), [page](https://verifymcp.io/servers/org-ailayoffs-ai-layoffs/ailayoffs)

## Channel facts

- Endpoint: `https://ailayoffs.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1570 tokens (~392/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the AI Layoffs MCP server?

AI Layoffs is a hosted endpoint at https://ailayoffs.org/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "org-ailayoffs-ai-layoffs": {
      "url": "https://ailayoffs.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-ailayoffs-ai-layoffs": {
      "type": "http",
      "url": "https://ailayoffs.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-ailayoffs-ai-layoffs]
url = "https://ailayoffs.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-ailayoffs-ai-layoffs": {
      "type": "remote",
      "url": "https://ailayoffs.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-ailayoffs-ai-layoffs --url 'https://ailayoffs.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-ailayoffs-ai-layoffs:
    url: "https://ailayoffs.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-ailayoffs-ai-layoffs": {
      "Transport": "http",
      "Url": "https://ailayoffs.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-ailayoffs-ai-layoffs -t streamable-http -u 'https://ailayoffs.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-ailayoffs-ai-layoffs": {
      "type": "http",
      "url": "https://ailayoffs.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 72)

First indexed and scored.

## MCP tools (4)

### `get_ai_layoffs_index` (~94 tokens)

Get the 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.

### `count_ai_job_losses` (~122 tokens)

How many jobs has AI replaced?

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.

### `search_ai_layoff_events` (~707 tokens)

Search the AI layoffs register

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 primary source and its ailayoffs.org company page; set full_context for the longer context and caveats.

Input parameters:

- `attribution` (array): Keep only these attribution levels. 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…
- `company` (string): Company name or part of it, e.g. 'Klarna'.
- `counted_only` (boolean): Only events whose roles the register counts as AI-attributed (drops events that are reported but not counted).
- `country` (string): Country as recorded, partial match, e.g. 'United States', 'India', 'Sweden'. For US-based roles use us_only.
- `evidence_tier` (array): Keep only these evidence tiers. 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 corro…
- `execution` (array): Keep only these execution statuses. 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).…
- `full_context` (boolean): Also return each event's context paragraph and the register's caveats. Several times longer, so best with a small limit; get_company_ai_layoffs always includes them for one company.
- `limit` (integer): Maximum events to return (default 10, at most 50).
- `query` (string): Free text matched against the company, the stated reason, the context notes, sector, country and affected roles. Every word must appear. Example: 'customer service'.
- `role` (string): Affected function or occupation, partial match, e.g. 'customer service', 'engineering'.
- `sector` (string): Sector, partial match, e.g. 'Financial', 'Software'.
- `since` (string): Earliest event date, inclusive: YYYY, YYYY-MM or YYYY-MM-DD.
- `sort` (string): newest first (default), oldest first, or the largest disclosed cut first.
- `until` (string): Latest event date, inclusive: YYYY, YYYY-MM or YYYY-MM-DD.
- `us_only` (boolean): Only events whose affected roles are US-based.

### `get_company_ai_layoffs` (~129 tokens)

Did this company cut jobs because of AI?

Did a specific company cut jobs because of AI? Returns the register's verdict for that company (explicit, mixed or blamed), the roles it disclosed vs the roles counted as AI-attributed, and every recorded event with the employer's own words and primary source. 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.

Input parameters:

- `company` (string, required): Company name, e.g. 'Klarna', 'IBM', 'Salesforce'. Partial names work.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-ailayoffs-ai-layoffs/ailayoffs#diagnostics

## Score history

- 2026-09-27: 72

## Common questions

### What is the AI Layoffs MCP server?

AI Layoffs is an MCP server listed in the public MCP registry as org.ailayoffs/ai-layoffs. Source-cited register of layoffs linked to AI, plus a live 0-100 AI job-loss index. No key. This page covers its hosted endpoint (https://ailayoffs.org/mcp).

### Is the AI Layoffs MCP server safe to use?

AI 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 AI Layoffs MCP server expose?

AI Layoffs exposes 4 tools: get_ai_layoffs_index, count_ai_job_losses, search_ai_layoff_events, get_company_ai_layoffs. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.

### Does the AI Layoffs MCP server require authentication?

No. We connected to AI Layoffs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AI Layoffs MCP server still maintained?

AI Layoffs is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ailayoffs.org/mcp
- Website: https://ailayoffs.org/data#mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-ailayoffs-ai-layoffs/ailayoffs.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-ailayoffs-ai-layoffs/ailayoffs.json
- HTML version of this page: https://verifymcp.io/servers/org-ailayoffs-ai-layoffs/ailayoffs