MCP DriftGuard
Continuous integrity verification for MCP servers. Detect whether the security-relevant server running now still matches the server that was originally approved.
What it does
MCP DriftGuard is a standalone integrity-verification tool for Model Context Protocol servers.
An MCP endpoint can remain at the same URL while its effective security surface changes. New tools can appear, schemas can widen, descriptions can acquire additional authority, authentication requirements can change, resources and prompts can move, and TLS identity can change.
MCP DriftGuard records a deterministic approved baseline and compares the live MCP server against it later. Its central question is: Is the MCP server running now still the MCP server that was approved?
DriftGuard can detect added or removed tools, schema changes, annotation changes, security-sensitive description changes, resource and prompt changes, MCP protocol changes, endpoint identity changes, TLS certificate and public-key changes, authentication challenge changes, and authorization-metadata drift. Baselines are protected with deterministic hashing and can optionally be signed using Ed25519. Verification output can be produced in human-readable, JSON, or SARIF form for integration into CI and security workflows.
DriftGuard deliberately requires no LLM, DDC dependency, hosted account, or telemetry service. A meaningful security-relevant difference produces an explicit PASS, REVIEW, or FAIL result rather than silently accepting the changed surface.
Current status: v0.1 release candidate. Additional interoperability testing remains in progress.
Who it helps
MCP server operators, AI platform teams, security engineers, enterprise integration teams, developers approving third-party MCP servers, and organizations maintaining long-lived MCP deployments.