PatchPilot MCP
Related Servers
Alternatives to PatchPilot MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.356 npm4MIT
- AlicenseAqualityBmaintenanceVerifies npm packages for security risks before installation, checking advisories, install scripts, typosquatting, and other factors, providing safe/block verdicts.164 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.8 npmMIT
- AlicenseAqualityAmaintenanceLocal-first, zero-egress security scanner for AI-generated / "vibe-coded" JS/TS. Bundles Opengrep, Gitleaks & Trivy behind one CWE-keyed schema and adds AI-code-specific checks (client-side secret exposure, Supabase RLS, prompt-injection & LLM-output XSS sinks). No account, no telemetry.10109 npm47Apache 2.0
- AlicenseAqualityFmaintenanceDependency security & health auditing for AI agents with no account or API key required.22MIT
- AlicenseAqualityDmaintenanceActs as a security checkpoint for AI coding agents by intercepting package installations to verify existence, check against CVE databases, and block vulnerable or hallucinated dependencies before they reach your codebase. Provides seven security tools including pre-install gates, full project audits, safe version recommendations, and deep transitive dependency scanning for npm and PyPI packages.739 npm4MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with other tools. The tool's purpose is clearly and unambiguously defined.
With a single tool, naming consistency is trivially satisfied. The name 'check_package' follows a clear verb_noun style that would be consistent if extended.
The server has only one tool, which feels too thin for the implied scope of 'PatchPilot'—a name suggesting broader patching and management workflows. One tool is insufficient to provide a meaningful set of operations.
The tool only checks for the presence of known vulnerabilities but provides no ability to list details, assess multiple packages at once, or suggest remediation. This creates significant gaps for agents needing comprehensive security information.