Diff and poisoning detection for MCP servers: catch schema drift and prompt poisoning.
Scored across 2 tools
check_drift targets a specific pinned-hash comparison, while inspect runs a broader multi-stage audit. The overlap is limited to schema evaluation, but an agent might still wonder whether inspect includes drift detection, causing minor ambiguity.
Both tools share the actionguard_ prefix and use snake_case, but check_drift follows a verb_noun pattern while inspect is a bare verb, creating a minor inconsistency.
Two tools is on the low side for a protocol inspector; while each has a clear purpose, the surface feels thin and could benefit from additional operations like baseline management or report retrieval.
The server lacks any tool to set or update the pinned Dual-Hash required by check_drift, leaving a dead end. Core inspection tasks are covered, but baseline lifecycle and result retrieval are missing.
Verify whether an MCP server's tools schema or descriptions have drifted from a pinned Dual-Hash.
Inputs: url (required), pinnedSchemaHash (required).
Run a 5-stage continuous reliability, security, and schema audit of an MCP server or AI agent endpoint.
Inputs: url (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Monitor MCP servers, API contracts and AI outputs for schema drift. Alerts on breaking changes.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Cloudflare Workers MCP server: api-schema-drift-detector
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
Add one secure layer between your agents and this server.
