driftcheck
Related Servers
Alternatives to driftcheck
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceChecks AI agents' claims against primary evidence, with no model; observes only what you grant.8105 PyPIApache 2.0
- 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
- AlicenseAqualityCmaintenanceEnables agents to verify real-world assertions like content being posted or PRs merged by fetching live evidence from URLs and GitHub, returning a verified boolean plus raw evidence.35 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
- AlicenseAqualityBmaintenanceGives AI agents safe, bounded, non-blocking access to Linux sysadmin inspection tasks, including CPU, RAM and disk healthchecks, memory-safe log tailing with regex filtering, and user-level systemd service and timer auditing. All operations run without sudo or unrestricted root shells, avoiding interactive pager hangs and context window flooding.4132 PyPI1MIT
- AlicenseAqualityCmaintenanceProvides AI agents with real-time ground truth about what's actually running on the machine, including live agent sessions, listening TCP ports, loaded daemons, and system stats. It reads directly from the OS via fixed commands, ensuring agents never rely on stale docs or transcripts.575 npm1MIT
TDQS
Scored across 1 tool
There is only one tool, so misselection between tools is impossible. Its purpose (verifying factual claims in markdown against the live system) is clearly stated and bounded.
check_docs follows the verb_noun snake_case convention cleanly. With a single tool there is no risk of mixing naming styles.
The server is narrowly scoped to one operation, so a single tool is defensible rather than an oversight. However, a bare 1-tool surface is thin, and the described functionality (scope filtering, include_ok, single file vs directory) hints at variants that could have been separate tools.
The core check operation is fully described, covering paths, ports, systemd units, and Forgejo repos with line-level reporting. Gaps remain: there is no way to discover available scopes or list claims without running a full check, no ignore/configuration operation, and no separate mode for previewing what would be checked.