AI Layoffs
REMOTE · AILAYOFFS.ORG · SCANNED SEP 27
Source-cited register of layoffs linked to AI, plus a live 0-100 AI job-loss index. No key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
remote · ailayoffs.org
claude mcp add --transport http org-ailayoffs-ai-layoffs 'https://ailayoffs.org/mcp'
{
"mcpServers": {
"org-ailayoffs-ai-layoffs": {
"url": "https://ailayoffs.org/mcp"
}
}
} {
"servers": {
"org-ailayoffs-ai-layoffs": {
"type": "http",
"url": "https://ailayoffs.org/mcp"
}
}
} [mcp_servers.org-ailayoffs-ai-layoffs] url = "https://ailayoffs.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-ailayoffs-ai-layoffs": {
"type": "remote",
"url": "https://ailayoffs.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-ailayoffs-ai-layoffs --url 'https://ailayoffs.org/mcp' --transport streamable-http
mcp_servers:
org-ailayoffs-ai-layoffs:
url: "https://ailayoffs.org/mcp" {
"McpServers": {
"org-ailayoffs-ai-layoffs": {
"Transport": "http",
"Url": "https://ailayoffs.org/mcp"
}
}
} assistant mcp add org-ailayoffs-ai-layoffs -t streamable-http -u 'https://ailayoffs.org/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://ailayoffs.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ailayoffs.org | CN=YR2,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | RSA 2048 | SHA256-RSA | 52d0e627804037153e0e82ed00acd03b08e |
| SANs: ailayoffs.org | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ailayoffs.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| ailayoffs.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ailayoffs.org/mcp | Verified | 200 | |
| http (plaintext) | http://ailayoffs.org/mcp | HTTPS enforced | 308 | https://ailayoffs.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
count_ai_job_losses How many jobs has AI replaced? ~122
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_ai_layoffs_index Get the AI Layoffs Index ~94
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_company_ai_layoffs Did this company cut jobs because of AI? ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name, e.g. 'Klarna', 'IBM', 'Salesforce'. Partial names work. |
No output schema declared.
No examples provided.
search_ai_layoff_events Search the AI layoffs register ~707
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.