MCP Drift Sentry

Detect when the MCP servers and tool definitions your agent relies on silently change

Problem

A builder shipped a tool that watches when an MCP server changes what it tells your agent, a sign people have been burned: a server quietly updates descriptions or outputs, agent behavior shifts, and nobody knows which day or which field changed, so debugging is guesswork. This is distinct from model retirement; it targets silent changes at the tool-description layer.

Solution

Users register the MCP servers and tools they connect. The product periodically probes exposed tool definitions, descriptions, and sample outputs, diffs them against stored snapshots, produces readable change reports with notifications, and flags which agent flows are likely affected.

Users

Developers and automation teams connecting third-party MCP servers through Claude Code, Cursor, and similar tools

MVP

Register servers and schedule probes; capture tool lists and description text; textual diff and version snapshots; email alerts on change; basic impact hints

Revenue

Subscription by number of monitored servers; team plan with shared registry and Slack alerts; sponsored change feeds for MCP vendors

Why now

The MCP ecosystem is exploding with uneven quality and no neutral change tracking; probing is lightweight enough for one developer to build