Skip to main content

MCP Drift Watch

Your AI agents trust what MCP servers say about their tools. Drift Watch makes sure it's still what you approved.

An MCP server can change its tool descriptions at any time after you approve it: a "rug pull". The AI model reads those descriptions as instructions, so a changed description can tell it to read files or send data somewhere. Nothing in MCP tells you when this happens.

Drift Watch pins every approved server by a SHA-256 fingerprint of everything the model reads:

  • the tool names and descriptions
  • the parameters
  • the server's instructions
  • how the server is started or reached

When any of it changes, the server is frozen and you get an alert. It stays frozen until a person looks at the change and approves or rejects it.

Install

uv tool install mcp-drift-watch          # or: pipx install mcp-drift-watch
driftwatch --version

The package is called mcp-drift-watch, and the command is driftwatch. A different, unrelated package on PyPI is called driftwatch, so pip install driftwatch and uvx driftwatch install that one, not this.

Optional parts:

  • mcp-drift-watch[web] adds the review site and the HTTP gateway
  • mcp-drift-watch[postgres] adds a hosted Postgres database, instead of a local SQLite file

Quick start

List the servers you approved in servers.yaml. Write secrets as ${VAR}: they're read from the environment and never stored.

servers:
  - name: notes
    transport: stdio
    command: npx
    args: ["-y", "@example/notes-mcp@1.4.2"]   # pin the version
  - name: tickets
    transport: http
    url: https://tickets.example.com/mcp
    headers: {Authorization: "Bearer ${TICKETS_TOKEN}"}
driftwatch pin servers.yaml       # approve what's there now, pinned by fingerprint
driftwatch check servers.yaml     # later: compare with the approved version (exit 1 if anything changed)
driftwatch diff notes             # what changed, with red flags and OWASP MCP Top 10 IDs
driftwatch approve notes --fingerprint <id>   # the id diff shows; or: driftwatch reject notes

check approves nothing, so it fits a CI job or a cron.

Before you start: what Drift Watch trusts

  • servers.yaml is like code. pin and check start the programs it names, and each ${VAR} hands that environment variable to them. Only use a servers.yaml you trust: never one from someone else's pull request.
  • A .env file in the current folder is read too (keys and settings). Trust it like servers.yaml.
  • The first pin trusts what the server serves at that moment. It warns about high red flags in that first version, and driftwatch diff <server> shows them.
  • The review site and the HTTP gateway have no sign-in. They answer only on 127.0.0.1 and refuse web pages, but any program on your computer can use them.

What else is included

  • AI second opinion: driftwatch review notes labels a change, quotes the risky text and gives a reason. It uses Claude Haiku with your own ANTHROPIC_API_KEY (or OPENROUTER_API_KEY), for about $0.0005 per change, within a monthly budget you set. Without a key, it uses a local model through Ollama if one is running. It never approves anything: only a person does.
  • Alerts: driftwatch check servers.yaml --review --alert sends each change once to Slack (an incoming webhook) and by email.
  • Scheduled watcher: driftwatch watch servers.yaml checks only the servers that are due, by risk, from every 6 hours to every 7 days.
  • Review site: driftwatch serve shows the approved list, the alerts, and for each change a side-by-side diff with hidden text highlighted, plus Approve and Reject buttons. It listens on 127.0.0.1 only.
  • Guard, for agents you write: driftwatch.guard wraps the MCP Python SDK client, so the model only ever sees approved tools, even from the SDK's cache. Calls with unapproved arguments are refused before they leave.
  • Gateway, for apps you can't change (like desktop AI apps and IDEs): driftwatch gateway stdio <server> or driftwatch gateway http stands between the app and its servers. It passes on only approved tools and calls. It starts a local server only if its launch command was approved.
  • Login setup check: driftwatch conform servers.yaml checks remote servers' published OAuth metadata against the MCP authorization spec. It sends only GET requests for public documents.

driftwatch export --lock approved.lock.json writes the approved list that the guard and the gateway enforce.

What it never does

  • Passive only. It reads what a server publishes to every client. No login attempts, and no attack traffic.
  • No telemetry. The CLI sends nothing to us. It contacts only your servers (and, with conform, the login servers they name), plus your AI provider, a local model, Slack and email when you turn those on.
  • The AI never approves. It only gives a second opinion.

Limits

  • Drift Watch compares what a server says about its tools, never its source code. A change to what a tool does, with the same description, isn't seen. Neither are instructions inside a tool's results.
  • It pins tools and server instructions, not prompts or resources.
  • The gateway checks tool lists and tool calls. Through gateway stdio, requests that start from the server, such as asking the app's model to write something or asking the user for input, pass through unchecked.

License

Apache-2.0

Metadata

Release files for mcp-drift-watch 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-drift-watch 0.1.0
File Size Uploaded Provenance Actions
mcp_drift_watch-0.1.0.tar.gz 138.7 kB With provenance Details for mcp_drift_watch-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-drift-watch 0.1.0
File Interpreter ABI Platform Actions
mcp_drift_watch-0.1.0-py3-none-any.whl Python 3 none any Details for mcp_drift_watch-0.1.0-py3-none-any.whl

Total release size: 292.8 kB

Release files / mcp_drift_watch-0.1.0.tar.gz

Download URL mcp_drift_watch-0.1.0.tar.gz
Size 138.7 kB
Tags Source
SHA-256 checksum
How to use checksums
52c21294c2e6e4b1d3b0cc9584b168ac94a0af013ece4d33e0a513c9f7f0b3a3
BLAKE2b-256 checksum
How to use checksums
0a4cd006da0c82dfd874615caac0cefa25e49267c334b60bd7764e0dbf8641df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

Release files / mcp_drift_watch-0.1.0-py3-none-any.whl

Download URL mcp_drift_watch-0.1.0-py3-none-any.whl
Size 154.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b909743d7f65b5cdb76c3cf07e9b463d775464461d1d9e55eb54cf0851b162da
BLAKE2b-256 checksum
How to use checksums
e64c8b8520b3eec344bb8e8f2cf6780f7048f4563ed05212461ede81e914a666
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

Security for mcp-drift-watch 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcp_drift_watch-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page