driftwatch-mcp

MCPcommunity
v0.1.2io.github.dhughes6071UnknownUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Reads these credentials
  • ANTHROPIC_API_KEYAPI keyoptional

    Optional. Adds LLM-synthesized migration steps on top of the deterministic results. The server works fully without it.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.dhughes6071
LicenseUnknown
Version0.1.2
Sourcenpm+mcp-registry
npmdriftwatch-mcp
GitHubdhughes6071/driftwatch
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.1.2 · 28d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev0.1.2 · 28d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

check_packageCheck 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).

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).

No input schema was published for this tool.

get_migration_deltaGiven 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.

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.

No input schema was published for this tool.

2 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

2 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-14 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.