See it in action.
01 — Open the hosted console with sample watches, live KPIs, and breaking counts — the same views your on-call team uses daily.
Contract drift monitoring
DriftGuard watches live REST and MCP endpoints, classifies every diff, and sends breaking-only alerts. Start free with the open-source MCP client — add hosted watches when you need continuous checks and a fleet console.
Monitor the APIs and MCP servers your agents depend on
The watchtower
Vendor APIs and MCP tool catalogs change on their schedule — not yours. DriftGuard turns silent schema changes into classified, actionable alerts.
01 — Open the hosted console with sample watches, live KPIs, and breaking counts — the same views your on-call team uses daily.
02 — REST APIs and MCP servers in a single watch list with status dots, sparkline history, and breaking counts at a glance.
03 — Required field removed pages on-call. Optional param added logs as warning. Description tweaks stay info.
04 — Track tools/list schema changes before Cursor agents break in production. Same watch model as REST OpenAPI.
05 — Slack, PagerDuty, webhooks, and Jira with breaking-only filters. Webhook v2 includes agentAction hints for each change.
Teams we power
From agent builders to platform teams — catch external dependency drift before production traffic does.
Stripe, GitHub, Twilio — live OpenAPI watches without manual spec audits.
tools/list catalog drift before agents break in prod.
Fail builds when production dependencies aren't watched.
Breaking-only pages — not description tweaks or HTTP blips alone.
Portfolio Compass, Insights dashboard, and Needs Review queue in the console.
200 watches, 5-minute checks, and fleet-wide coverage.
Vendor APIs and MCP servers change on their schedule — not yours.
Add checks in order — local and CI first, hosted watches when you need always-on monitoring.
Replay drift scenarios in tests before production.
How-to → Gate 2Stop runaway agent tool loops and trip on active drift.
How-to → Gate 3Lint MCP tool manifest changes in PRs.
How-to → Gate 4Check prompts against removed schema fields; draft PRs on hosted.
How-to →Three steps from signup to your first breaking alert.
Paste any HTTPS API or MCP endpoint. Import from catalog or mcp.json.
Scheduled checks capture schema shape and compare against the last snapshot.
Webhooks fire on breaking drift. Acknowledge and resolve incidents from the console.
Self-host free forever, or let us run the watches.
compare_json + MCP toolsEverything you need to evaluate, integrate, and scale monitoring.
Local-first path: install, diff, MCP, first watch, CI gate.
Getting started → IntegrationsGitHub Actions, Cursor MCP, Slack, GitLab, and webhooks.
Integrations → CITrial session, workflow snippet, and coverage assert.
CI setup → DemoLive console with sample watches, drift, and incidents.
Open demo → HubGuides, changelog, activation, and solution playbooks.
Resource hub →Unlock hosted watches, MCP monitoring, and breaking-only alerts. Start on one endpoint — scale to fleet-wide coverage when you're ready.