# driftwatch (npm · driftwatch-mcp)

What broke between two dependency versions, with a citation for every claim. No API key needed.

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

## Components

- npm · `driftwatch-mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/dhughes6071-driftwatch/driftwatch-mcp.md), [page](https://verifymcp.io/servers/dhughes6071-driftwatch/driftwatch-mcp)

## Channel facts

- Registry: `npm`
- Package: `driftwatch-mcp`
- Version: `0.1.2`
- 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-09-21.

- **Supply Chain Security**: 98/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.
  - 34 of 105 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 279 tokens (~139/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 driftwatch MCP server?

driftwatch runs locally as an npm package, launched with npx -y driftwatch-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 dhughes6071-driftwatch -- npx -y driftwatch-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dhughes6071-driftwatch": {
      "command": "npx",
      "args": [
        "-y",
        "driftwatch-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dhughes6071-driftwatch": {
      "command": "npx",
      "args": [
        "-y",
        "driftwatch-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dhughes6071-driftwatch -- npx -y driftwatch-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dhughes6071-driftwatch --command npx --arg -y --arg driftwatch-mcp
```

### Hermes

```yaml
mcp_servers:
  dhughes6071-driftwatch:
    command: "npx"
    args: ["-y", "driftwatch-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dhughes6071-driftwatch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "driftwatch-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dhughes6071-driftwatch -t stdio -c npx -a -y driftwatch-mcp
```

### Other

```json
{
  "mcpServers": {
    "dhughes6071-driftwatch": {
      "command": "npx",
      "args": [
        "-y",
        "driftwatch-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-09-21 (score 85, +1)

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

### 2026-09-18 (score 84, +1)

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

### 2026-09-16 (score 83, +1)

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

### 2026-09-14 (score 82, +1)

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

### 2026-09-12 (score 81, +1)

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

### 2026-09-10 (score 80, +1)

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

### 2026-09-08 (score 79, +1)

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

### 2026-09-06 (score 78, +1)

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

## MCP tools (2)

### `check_package` (~124 tokens)

Verify a package before installing

Check whether a package actually exists and is safe to install. Returns existence, latest version, deprecation status, security advisory count, and a `suspicious` flag when the name resembles a popular package but behaves like a typosquat (no repository, placeholder version, one release). Call this before running any install command for a package you have not verified in this session -- LLM-generated package names are a known malware vector.

Input parameters:

- `ecosystem` (string, required): Which package registry the package lives in.
- `name` (string, required): Package name exactly as it would be installed.

### `get_migration_delta` (~155 tokens)

What broke between two versions

Given a package and two versions, return the breaking changes between them: removed and renamed symbols, concrete before/after code fragments, and security advisories the upgrade resolves. Every claim links to a primary source. Use this BEFORE writing or fixing code against a library version you are unsure about, and whenever a build fails after a dependency upgrade. It is far cheaper than iterating on failed builds.

Input parameters:

- `ecosystem` (string, required): Which package registry the package lives in.
- `from` (string, required): The version currently installed, e.g. 18.2.0
- `name` (string, required): Package name.
- `to` (string, required): The version being upgraded to, e.g. 19.0.0

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dhughes6071-driftwatch/driftwatch-mcp#diagnostics

## Score history

- 2026-09-21: 85
- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 75
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 71
- 2026-08-25: 70
- 2026-08-24: 70
- 2026-08-23: 55

## Common questions

### What is the driftwatch MCP server?

driftwatch is an MCP server listed in the public MCP registry as io.github.dhughes6071/driftwatch. What broke between two dependency versions, with a citation for every claim. No API key needed. This page covers its npm package (driftwatch-mcp).

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

driftwatch scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 driftwatch MCP server expose?

driftwatch exposes 2 tools: check_package, get_migration_delta. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.

### Is the driftwatch MCP server still maintained?

driftwatch is still listed as active in the MCP registry. We last reached this channel on 21 September 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 driftwatch MCP server under?

driftwatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/driftwatch-mcp
- Socket report: https://socket.dev/npm/package/driftwatch-mcp
- Repository: https://github.com/dhughes6071/driftwatch
- Changelog RSS feed: https://verifymcp.io/servers/dhughes6071-driftwatch/driftwatch-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dhughes6071-driftwatch/driftwatch-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dhughes6071-driftwatch/driftwatch-mcp