# Driftline (npm · @aidriftline/driftline)

Retirement dates and replacements for OpenAI, Anthropic, Google and 5 more, plus Bedrock and Azure.

- Trust score: 81/100 (high trust)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@aidriftline/driftline`: 81/100 (this document), [markdown](https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline.md), [page](https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline)

## Channel facts

- Registry: `npm`
- Package: `@aidriftline/driftline`
- Version: `0.11.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 84/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to AI-Driftline/driftline).
  - License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 830 tokens (~276/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Driftline MCP server?

Driftline runs locally as an npm package, launched with npx -y @aidriftline/driftline mcp. 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 ai-driftline-driftline -- npx -y @aidriftline/driftline mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ai-driftline-driftline": {
      "command": "npx",
      "args": [
        "-y",
        "@aidriftline/driftline",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-driftline-driftline": {
      "command": "npx",
      "args": [
        "-y",
        "@aidriftline/driftline",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ai-driftline-driftline -- npx -y @aidriftline/driftline mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-driftline-driftline": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@aidriftline/driftline",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-driftline-driftline --command npx --arg -y --arg @aidriftline/driftline --arg mcp
```

### Hermes

```yaml
mcp_servers:
  ai-driftline-driftline:
    command: "npx"
    args: ["-y", "@aidriftline/driftline", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ai-driftline-driftline": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@aidriftline/driftline",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-driftline-driftline -t stdio -c npx -a -y @aidriftline/driftline mcp
```

### Other

```json
{
  "mcpServers": {
    "ai-driftline-driftline": {
      "command": "npx",
      "args": [
        "-y",
        "@aidriftline/driftline",
        "mcp"
      ]
    }
  }
}
```

## 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-21 (score 81, 0)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.11.5 → 0.11.6

### 2026-11-20 (score 81, +1)

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

### 2026-11-19 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 65, +12)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass
- [functional] Package version: 0.11.4 → 0.11.5

### 2026-11-17 (score 53, −26)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.10.0 → 0.11.4
- [functional] Package version: 0.10.0 → 0.11.3
- [functional] Package version: 0.10.0 → 0.11.0

### 2026-11-16 (score 79, +27)

- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.9.3 → 0.10.0

### 2026-11-15 (score 52, −15)

- [security regression] Malware scan: pass → unverified
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → pass
- [functional] Package version: 0.8.0 → 0.9.3
- [functional] Package version: 0.8.0 → 0.9.2
- [functional] Package version: 0.8.0 → 0.9.1
- [functional] Package version: 0.8.0 → 0.8.1

### 2026-11-14 (score 67, +4)

- [security regression] Known CVEs: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 223 → 276
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.1 → 0.8.0
- [functional] Package version: 0.2.1 → 0.6.1
- [functional] Package version: 0.2.1 → 0.6.0
- [functional] Package version: 0.2.1 → 0.4.0
- [functional] Package version: 0.2.1 → 0.3.0

## MCP tools (3)

### `check_models` (~268 tokens)

Check model IDs for retirement

Look up OpenAI, Anthropic, Google, Mistral, xAI, Cohere, DeepSeek and Groq model IDs (and Amazon Bedrock, Vertex AI and Azure) and return, for each one, its retirement status, retirement date, days left and replacement. Use it before writing, changing or keeping a model ID in code, or when the user asks whether a model still works. To find the IDs inside a codebase use scan_project instead; to list everything retiring soon use upcoming_retirements. Read-only. Data comes from the providers' official deprecation pages, re-checked daily at aidriftline.com (fetched with a 4 s timeout, falling back to the copy in the package when offline). IDs not in the registry return status "unknown": no retirement is published for them, which does not prove the ID exists. Up to 100 IDs per call; extra IDs are ignored.

Input parameters:

- `ids` (array, required): Model IDs exactly as written in code, e.g. ["gpt-4o", "claude-sonnet-4-5", "models/gemini-2.5-pro"]. Provider prefixes (openai/, models/), Bedrock, Vertex and OpenRouter spellings and Claude short na…

Output parameters:

- `all_dates` (string)
- `models` (array)
- `next_step` (string): Present when a model has to move: how to test prompts on the replacement first
- `registry_checked` (string): Date the registry was last checked against the provider pages
- `registry_source` (string): live = aidriftline.com/models.json; bundled = the copy shipped in the package (used offline)

### `scan_project` (~252 tokens)

Scan a project for retiring model IDs

Scan a project folder for OpenAI, Anthropic, Google, Mistral, xAI, Cohere, DeepSeek and Groq model IDs (and Amazon Bedrock, Vertex AI and Azure) in code and config files and report the ones that are retired, retiring soon, deprecated or being re-routed, with file and line, most urgent first. Use it to audit a repository or before a release. For IDs you already know use check_models; for a time-based list use upcoming_retirements. Read-only: reads files on this machine and never changes them. Scans subfolders recursively, skips .git, node_modules, vendor, dist, build and similar folders, and files over 1 MB. Mentions in .md and .txt files are marked in_docs. Returns at most 200 findings (truncated: true when cut). Fails with an error if the path does not exist.

Input parameters:

- `include_ok` (boolean): Also list models with no retirement announced (status active or unknown). Default false.
- `path` (string): Absolute path of the folder to scan. Defaults to the server's working directory, which may not be the user's project, so pass it explicitly.

Output parameters:

- `all_dates` (string)
- `findings` (array)
- `flagged` (number)
- `model_references` (number): All model ID mentions found, before filtering
- `next_step` (string): Present when a model has to move: how to test prompts on the replacement first
- `registry_checked` (string): Date the registry was last checked against the provider pages
- `registry_source` (string): live = aidriftline.com/models.json; bundled = the copy shipped in the package (used offline)
- `scanned` (string)
- `truncated` (boolean)

### `upcoming_retirements` (~236 tokens)

List upcoming model retirements

List OpenAI, Anthropic, Google, Mistral, xAI, Cohere, DeepSeek, Groq, Amazon Bedrock, Vertex AI and Azure models whose retirement or re-routing date falls in the next N days, soonest first, with replacement for each. Use it to answer "what is being retired soon?" or to plan migrations. It does not look at code: use scan_project for that, or check_models for specific IDs. Read-only. Models already past their date are not included (check_models reports those as retired). Anthropic "not before" dates are left out because those models are still active.

Input parameters:

- `days` (number): Look-ahead window in days, 1 to 3650. Default 90.
- `provider` (string): Only this provider's own API (openai, anthropic, google, mistral, xai, cohere, deepseek, groq), or "bedrock" / "vertex" / "azure" for Amazon Bedrock's, Google Vertex AI's or Microsoft Azure's dates (…

Output parameters:

- `all_dates` (string)
- `count` (number)
- `days` (number)
- `models` (array)
- `next_step` (string): Present when a model has to move: how to test prompts on the replacement first
- `registry_checked` (string): Date the registry was last checked against the provider pages
- `registry_source` (string): live = aidriftline.com/models.json; bundled = the copy shipped in the package (used offline)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 65
- 2026-11-17: 53
- 2026-11-16: 79
- 2026-11-15: 52
- 2026-11-14: 67
- 2026-11-13: 63
- 2026-11-12: 78
- 2026-11-11: 62

## Common questions

### What is the Driftline MCP server?

Driftline is an MCP server listed in the public MCP registry as io.github.AI-Driftline/driftline. Retirement dates and replacements for OpenAI, Anthropic, Google and 5 more, plus Bedrock and Azure. This page covers its npm package (@aidriftline/driftline).

### Is the Driftline MCP server safe to use?

Driftline scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Driftline MCP server expose?

Driftline exposes 3 tools: check_models, scan_project, upcoming_retirements. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

### Is the Driftline MCP server still maintained?

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

### What licence is the Driftline MCP server under?

Driftline declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

### What did VerifyMCP test on the Driftline MCP server?

VerifyMCP ran 16 checks on Driftline, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@aidriftline/driftline
- Socket report: https://socket.dev/npm/package/@aidriftline/driftline
- Repository: https://github.com/AI-Driftline/driftline
- Website: https://aidriftline.com/agents/
- Changelog RSS feed: https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline.json
- HTML version of this page: https://verifymcp.io/servers/ai-driftline-driftline/aidriftline-driftline
