Driftline
NPM · @AIDRIFTLINE/DRIFTLINE
Retirement dates and replacements for OpenAI, Anthropic, Google and 5 more, plus Bedrock and Azure.
Available components
Last scanned (15 hours ago)
Scores higher than 69% of npm servers
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AI-Driftline/driftline). View diagnostics → Pass
- License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.11.5 → 0.11.6 functional
- 20 Nov 26 +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.
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- Package version: 0.11.4 → 0.11.5 functional
- 17 Nov 26 −26
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- 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 functional
- 16 Nov 26 +27
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.9.3 → 0.10.0 functional
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- 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 functional
- 14 Nov 26 +4
- Known CVEs: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 223 → 276 ▼ functional
- 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 functional
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 21 Nov 2026 · Analysed npm/@aidriftline/driftline@0.11.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AI-Driftline/driftline |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AI-Driftline/driftline/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 4031670976 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:69121658227b35bf8fbd1e75246a4619d3d00e71e185d92ab3407d39092676e9d1e7dbb65ec30cc0540487de4edf21d3b133bac3442079827f97a3be5 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_models Check model IDs for retirement ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| all_dates | string | – | – |
| models | array | yes | – |
| next_step | string | – | Present when a model has to move: how to test prompts on the replacement first |
| registry_checked | string | yes | Date the registry was last checked against the provider pages |
| registry_source | string | yes | live = aidriftline.com/models.json; bundled = the copy shipped in the package (used offline) |
No examples provided.
scan_project Scan a project for retiring model IDs ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| all_dates | string | – | – |
| findings | array | yes | – |
| flagged | number | yes | – |
| 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 | yes | – |
| truncated | boolean | – | – |
No examples provided.
upcoming_retirements List upcoming model retirements ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 (… |
| Name | Type | Req | Description |
|---|---|---|---|
| all_dates | string | – | – |
| count | number | yes | – |
| days | number | yes | – |
| models | array | yes | – |
| 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) |
No examples provided.
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.
npm · @aidriftline/driftline
claude mcp add ai-driftline-driftline -- npx -y @aidriftline/driftline mcp
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.