Docs Auditor MCP
Related Servers
Alternatives to Docs Auditor MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes tools that scan a repository's manifests, CI workflows and layout to generate truthful AGENTS.md/CLAUDE.md agent instructions, then audit those docs for drift such as dead commands, undocumented scripts and CI mismatches. Enables agents to keep their own onboarding documentation accurate and CI-verifiable instead of hand-written and rotting.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, outline, read, and patch living documentation sections across multiple linked repos, check drift status, review recent changes, and query a cross-repo code graph. Writes respect per-user API key permissions and configurable trust modes, keeping shared docs in sync with code.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to check their own instruction files for drift before a run, returning findings with file and line for stale counts, missing files, broken links, and missing commands. Also lets agents list which agent docs get inspected.14 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents and developers to independently verify code and documentation claims against the repository, producing evidence-backed audit reports and pull-request checks.14MIT
- AlicenseNot gradedqualityBmaintenanceChecks AGENTS.md and CLAUDE.md against a repository's actual file tree and package.json, reporting missing referenced paths and scripts so agent instructions stay accurate. Returns deterministic findings with file, line, and exact source text through a single tool.60 npmMIT
- AlicenseBqualityCmaintenanceEnables AI coding agents to perform evidence-based, read-only audits of supported software projects by exposing bounded project inventory and static-analysis findings for discovery, code review, integration tracing, security, and tests. Reports are returned as Markdown or JSON directly in the tool response, with no code executed or files written.817 npmMIT
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: inspecting structure, reading docs, cross-checking snippets, analyzing issues, generating patches, and applying patches. The main overlap is run_full_audit, which duplicates the individual pipeline steps and also returns fix patches, but its description makes the orchestration role clear enough to avoid serious misselection.
All tool names use snake_case and follow a predictable verb-first pattern: fetch_*, read_*, cross_check_*, analyze_*, generate_*, run_*, apply_*. The convention is consistent throughout the set.
Seven tools is well-scoped for a docs auditing server, with each tool covering a meaningful step in the audit workflow. The full-audit convenience tool is justified alongside the granular tools rather than feeling like padding.
The surface covers the core docs audit lifecycle: inspect repo structure, read docs, verify snippets, search issues, generate patches, and apply them. Minor gaps remain, such as no standalone env-drift tool despite run_full_audit mentioning it, and patch application limited to local checkouts rather than remote PR creation.