$ loading_
Compare documentation claims against current source tree facts to detect architecture drift.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Architecture Drift MCP" yet — see the docs or source repo.
Compare the key claims in this architecture document with the actual implementation in the current source tree. List mismatches and attach traceable evidence locations for each finding.
A discrepancy list showing where documentation claims conflict with source facts, with evidence references.
Using the documented claims, check whether the current codebase has drifted architecturally, focusing on module boundaries, dependencies, and key component locations.
An architecture drift report showing which claims still hold and which no longer match the codebase.
Compare the system structure described in the documentation with the current source tree item by item, and produce evidence-based conclusions for code or technical review.
A structured comparison suitable for quickly explaining gaps between docs and implementation during review.
Developers or technical leads can use it after documentation has aged to verify whether architectural descriptions still match the current source tree, reducing misleading technical docs.
When a team suspects implementation has drifted from the original design, this tool helps locate deviations and supporting evidence by comparing documented claims with source facts.
Before architecture reviews or refactoring plans, teams can use it to organize mismatches between documentation and implementation, providing a basis for updating docs or code.
It compares evidence-linked documentation claims with facts observed in the current source tree to identify architecture drift or documentation mismatch.
Based on the description, it compares claims in documentation against actual facts in the current source tree. For detailed comparison scope and rules, see the source repository.
The provided materials do not include installation steps, runtime requirements, or key requirements. Please see the source repository for prerequisites.
Detect doc drift and verify claims for MCP tools deterministically.
Scan codebases for incompleteness and quantify LLM context drift risk.
Check documentation against source code and suggest fixes for drift.
Audit project portfolios against GitHub conversationally to detect drift and anomalies.
Analyze codebases to generate READMEs, API docs, diagrams, and changelogs.
Understand codebases, detect conventions, and retain decisions across sessions.