Detect doc drift and verify claims for MCP tools deterministically.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "DocGuard" MCP server from askskill: Run: claude mcp add 'io-github-raccioly-docguard' -- npx -y docguard-cli
Developers or DevOps teams can use it before releasing an MCP tool to check whether descriptions and documentation have drifted and whether feature claims are consistent.
When a team disagrees on what an MCP tool actually supports, it can score, explain, and verify claims to help locate the source of inconsistency.
It performs deterministic doc-drift detection for MCP tools and provides capabilities such as guard, score, explain, verify-claims, and diagnose.
Based on the provided description, it focuses on doc drift, claim verification, explaining differences, and diagnosing issues for MCP tool documentation consistency.
The provided materials do not include installation steps, runtime details, or key requirements; see the source repository.
Check documentation against source code and suggest fixes for drift.
Compare documentation claims against current source tree facts to detect architecture drift.
Validate AI-generated code against real codebases before bugs reach runtime.
Scan codebases for incompleteness and quantify LLM context drift risk.
Audit project portfolios against GitHub conversationally to detect drift and anomalies.
Statically inspects MCP tool metadata for misleading instructions, hidden capabilities, and schema drift.