Skip to main content
Glama
ElDiegolar

MCP-Vetting

by ElDiegolar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MCP-Vetting

No user-submitted related servers found.

    Related Servers

    • MCPskills

      BeBraveBeKind
      A
      license
      A
      quality
      D
      maintenance
      Pre-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.
      9
      85 npm
      1
      MIT

    • tooltrust-mcp

      AgentSafe-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      Scans 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.
      19
      MIT

    • mcp-radar

      XiaoMoDern
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -

    • mcp-fortress

      mcp-fortress
      A
      license
      Not graded
      quality
      D
      maintenance
      Scans MCP servers for security vulnerabilities, prompt injection, and tool poisoning, providing risk scores and protection.
      4
      MIT
    • oathe-mcp by oathe-ai

      oathe-mcpofficial

      oathe-ai
      A
      license
      A
      quality
      C
      maintenance
      MCP server for https://oathe.ai security audits. Runtime behavioral analysis and security scanner for Ai systems. Check trust scores before installing MCP servers, plugins, or AI agent skills.
      5
      9 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources