MCP Drift Observatory
See whether a public MCP server changed the tools it declares: when, how often, and exactly which names, descriptions or schemas moved. Read-only, no sign-in.
- Category
- Developer Tools
- Primary Subcategory
- Observability, Monitoring & Incident Response
Integration details
Description
An MCP server's tool names and descriptions go straight into the model's context. When a server quietly rewrites them, what your agent is told to do changes with nothing changing on your side. This is how rug-pulls and poisoned tools happen. The MCP Drift Observatory reads public MCP servers every night, hashes the tools each one declares, and records every change. Ask Claude about any server: - Has it changed its tools, when, and how many times (drift_check)? - What exactly changed: which tool, and whether its name, description, schema or annotations moved (drift_diff)? - Read it right now and compare with the stored baseline (drift_probe). - How much of the ecosystem is covered (drift_status), and hash a tool list yourself with the same canonical bytes (drift_hash). Every tool is read-only and needs no account. The observatory can only see servers that answer without a login, so it reports "not observed" rather than guessing, and says how many servers sit behind a login. Changes are also published as a signed public feed and a public archive. To pin every server in your own project, including private ones, use the free MCP Drift Guard GitHub Action (getvda-ai/mcp-drift-guard).
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Primary Subcategory
- Observability, Monitoring & Incident Response
- Secondary Subcategories
- None listed
- Access
- No account required
- First tracked
- 2026-11-18
- Tool count
- 6
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competing in Claude Observability, Monitoring & Incident Response
View Category6 tools agents can invoke
MCP Drift Observatory Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve MCP Drift Observatory's Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are MCP Drift Observatory alternatives on Claude?
As of 2026-11-19, MCP Drift Observatory competes with Datadog, mcp.betterstack.com, Grafana Cloud, incident.io, PagerDuty, Coralogix, Rootly, New Relic and 92 more in Claude Observability, Monitoring & Incident Response, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.