No user-submitted related servers found.
Scored across 6 tools
Most tools have sharply distinct purposes, and the one overlapping pair—vet_mcp_server vs static_scan_tools—is clearly differentiated by scope (full gate chain vs static-only) and by explicit when-to-use guidance. The remaining tools (classification, egress, canonicalization, rule listing) are cleanly separated and unlikely to be confused.
Five of six tools follow a predictable verb-oriented snake_case pattern (classify_sensitive_tools, check_egress_url, canonicalize_json, list_scan_rules, and roughly vet_mcp_server). static_scan_tools is a noun-phrase outlier, but the overall naming style is consistent and readable.
Six tools is well-scoped for the stated purpose: one comprehensive vetting entry point plus focused utilities for static scanning, policy preview, egress checks, canonicalization, and rules introspection. Each tool fills a distinct role without redundancy or bloat.
The toolset covers the full vetting decision, the static scan gate, sensitive-tool classification, outbound URL policy checks, canonicalization for signature/pin verification, and ruleset introspection. No obvious dead ends or missing operations prevent an agent from completing the typical vetting workflow.