MCP-Vetting
Related Servers
Alternatives to MCP-Vetting
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenancePre-install trust scoring & safety scanning for MCP servers, AI skills & npm packages — 15 signals incl. OSV/KEV/EPSS vuln intel and an auto-gate go/no-go.9191 npm1MIT
- AlicenseNot gradedqualityBmaintenanceScans MCP servers for prompt injection, supply chain attacks, excessive permissions, and code execution risks. Includes an offline blacklist that catches known-compromised packages like LiteLLM 1.82.7/1.82.8 and Trivy with zero latency.19MIT
- AlicenseAqualityBmaintenanceSecurity scanner for MCP servers: detects tool poisoning, hidden instructions, tool shadowing, excessive permissions, leaked secrets and weak transports before you install a server.4118 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables users to search and audit MCP servers by quality metrics such as installs, security, and activity, helping them find trustworthy servers and avoid ones with no installs.-
- AlicenseAqualityBmaintenanceSecurity for the MCP servers you use: detects tool poisoning, rug pulls, shadowing, secrets and supply-chain risk (OWASP MCP Top 10), with runtime guards and approved-server policy. Runs locally.17273 npmMIT
- AlicenseNot gradedqualityDmaintenanceScans MCP servers for security vulnerabilities, prompt injection, and tool poisoning, providing risk scores and protection.4MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: vetting remote vs local, retrieving cached verdicts, listing scanners, listing harnesses, and generating configs. No two tools overlap in what they do, and the descriptions reinforce their unique roles.
All tools follow a consistent verb_noun snake_case pattern: vet_server, vet_directory, get_verdict, list_scanners, list_harnesses, get_config. The verbs (vet, get, list) are descriptive and uniform.
With 6 tools, the set is well-scoped for a vetting framework, covering both operational actions and informational queries. There is no bloat or redundancy.
The tool surface covers the core lifecycle: vetting remote and local servers, retrieving cached results, enumerating available scanners and harnesses, and generating configuration. No obvious gaps hinder a user from completing a vetting workflow.