# AI-Safe Careers (remote · aisafe.careers)

AI exposure scores (0-100) for ~1,000 U.S. occupations, and recent AI-attributed layoffs.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `aisafe.careers`: 71/100 (this document), [markdown](https://verifymcp.io/servers/careers-aisafe-ai-exposure/aisafe.md), [page](https://verifymcp.io/servers/careers-aisafe-ai-exposure/aisafe)

## Channel facts

- Endpoint: `https://aisafe.careers/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-11-04.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 369 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the AI-Safe Careers MCP server?

AI-Safe Careers is a hosted endpoint at https://aisafe.careers/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 careers-aisafe-ai-exposure 'https://aisafe.careers/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "careers-aisafe-ai-exposure": {
      "url": "https://aisafe.careers/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "careers-aisafe-ai-exposure": {
      "type": "http",
      "url": "https://aisafe.careers/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.careers-aisafe-ai-exposure]
url = "https://aisafe.careers/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "careers-aisafe-ai-exposure": {
      "type": "remote",
      "url": "https://aisafe.careers/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add careers-aisafe-ai-exposure --url 'https://aisafe.careers/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  careers-aisafe-ai-exposure:
    url: "https://aisafe.careers/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "careers-aisafe-ai-exposure": {
      "Transport": "http",
      "Url": "https://aisafe.careers/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add careers-aisafe-ai-exposure -t streamable-http -u 'https://aisafe.careers/mcp'
```

### Other

```json
{
  "mcpServers": {
    "careers-aisafe-ai-exposure": {
      "type": "http",
      "url": "https://aisafe.careers/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-11-03 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 70)

First indexed and scored.

## MCP tools (3)

### `get_ai_exposure` (~134 tokens)

AI exposure for a job

Look up the AI Exposure Score (0-100) for a job title: its band (Low, Moderate, Elevated, High, Very High), percentile, example tasks that are automatable, augmentable or durable, and adjacent careers with their scores. Scores are precomputed estimates of how much of a role's tasks overlap with what AI can do, built from O*NET and published research; they are not predictions that a job will disappear. Cite "AI-Safe Careers" with the returned URL.

Input parameters:

- `job_title` (string, required): A job title, for example "registered nurse" or "data analyst".

### `search_occupations` (~78 tokens)

Search occupations

Find occupations whose titles match a search, with each one's AI Exposure Score, band and page URL. Use it when a job title is ambiguous, then call get_ai_exposure with the exact occupation.

Input parameters:

- `limit` (integer): How many matches to return (default 8).
- `query` (string, required): Words from a job title.

### `recent_ai_attributed_layoffs` (~94 tokens)

Recent AI-attributed layoffs

Recent layoffs where the company itself cited AI as a reason, from AI-Safe Careers' curated tracker, each with its date, approximate headcount and source. All-cause layoffs (layoffs.fyi, WARN notices) are tracked separately and are never included here, so these are not a count of all job cuts.

Input parameters:

- `limit` (integer): How many events to return (default 10).

## Diagnostics

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

## Score history

- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70

## Common questions

### What is the AI-Safe Careers MCP server?

AI-Safe Careers is an MCP server listed in the public MCP registry as careers.aisafe/ai-exposure. AI exposure scores (0-100) for ~1,000 U.S. occupations, and recent AI-attributed layoffs. This page covers its hosted endpoint (https://aisafe.careers/mcp).

### Is the AI-Safe Careers MCP server safe to use?

AI-Safe Careers scores 71 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-Safe Careers MCP server expose?

AI-Safe Careers exposes 3 tools: get_ai_exposure, search_occupations, recent_ai_attributed_layoffs. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.

### Does the AI-Safe Careers MCP server require authentication?

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

### Is the AI-Safe Careers MCP server still maintained?

AI-Safe Careers is still listed as active in the MCP registry. We last reached this channel on 4 November 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://aisafe.careers/mcp
- Website: https://aisafe.careers/
- Changelog RSS feed: https://verifymcp.io/servers/careers-aisafe-ai-exposure/aisafe.xml
- Changelog JSON feed: https://verifymcp.io/servers/careers-aisafe-ai-exposure/aisafe.json
- HTML version of this page: https://verifymcp.io/servers/careers-aisafe-ai-exposure/aisafe