PrufGate MCP
OfficialRelated Servers
Alternatives to PrufGate MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes repository reconnaissance tools — file listing and verbatim reading, regex search, dependency-tree parsing across Python/Node/Rust/Go, and test-coverage ingestion — so agents can gather line-numbered evidence from real source files. This lets an audit pipeline physically re-verify every claim and drop findings that cannot be located in the code.MIT

Zof MCP serverofficial
AlicenseNot gradedqualityBmaintenanceGives a compatible coding agent read-only access to bounded local verification of changes inside a single host-chosen workspace, exposing six stdio tools that inspect capabilities, static checks, impact analysis, policy evaluation, evidence generation, and suggested tests without shell access, plugin loading, or repository upload.97 npmApache 2.0- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scan code for security and quality issues and receive machine-readable reports with suggested fixes and verification criteria.80 npm2MIT
- AlicenseAqualityDmaintenanceRead-only MCP tools for coding agents to audit deployment targets, detect fabricated code, review backlog, database schema, analytics, ML models, architecture docs, and decision lenses.1113 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes thirty callable tools that let any MCP client audit server manifests, detect poisoned tool descriptions, config files and long-term memory, catch tool rug-pulls, check known vulnerabilities and package authenticity, and statically screen tool code for SSRF, path traversal and command injection risk. It also simulates whether a proposed agent action should auto-approve or be held for human review.MIT
TDQS
Scored across 10 tools
Each tool has a distinct role: individual engines, composite scans, rule explanation, and report reading. There is minor overlap between fast_scan/full_scan and the engine-specific tools, but the descriptions clarify scope as changed files vs whole workspace vs single engine.
All ten tools use the same prufgate_ prefix and snake_case formatting, with no mixed conventions. Whether the name is action-oriented or an engine label, it follows the same predictable namespace pattern.
Ten tools map cleanly to six engines plus aggregate scans, explanation, and summary reporting. The count is well-scoped, with no obvious filler or redundant tools.
The surface covers individual engines 1-6, aggregate scans, rule explanation, and summary report reading. Minor gaps remain around programmatic findings access, false-positive recording, and rule listing, but core scanning workflows are covered.