Skip to main content
Glama
msaad00

agent-bom

by msaad00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to agent-bom

No user-submitted related servers found.

    Related Servers

    • agent-audit

      piiiico
      A
      license
      Not graded
      quality
      C
      maintenance
      Security scanner for MCP servers. Detects prompt injection, command injection, auth bypass, and excessive permissions across tools, resources, and prompts.
      38
      2
      MIT

    • MCP Shield

      rob925
      A
      license
      C
      quality
      B
      maintenance
      Security scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.
      2
      1
      MIT

    • MCPAmpel

      MCPAmpel
      A
      license
      A
      quality
      D
      maintenance
      A security scanner that evaluates installed MCP servers for vulnerabilities by aggregating findings from 16 scanning engines into detailed trust scores. It enables users to scan their local AI agent configurations or specific repository URLs for potential security risks.
      4
      2
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check for single-package CVE pre-check, scan for comprehensive AI-BOM generation, remediate for fix plans, policy_check for policy evaluation, compliance for framework posture, generate_sbom for SBOM output, intel_lookup for advisory details, and exposure_paths for graph data. No overlapping or ambiguous boundaries.

    Naming Consistency4/5

    All tool names are lowercase and use snake_case, but not strictly verb_noun (e.g., compliance and exposure_paths are nouns). However, most are action-oriented and predictable, so the set is readable and consistent in style with minor deviations.

    Tool Count5/5

    With 8 tools, the server is well-scoped for an AI supply chain security domain. Each tool addresses a distinct stage or aspect (pre-check, full scan, SBOM, compliance, policy, remediation, intel, exposure paths), and none feel redundant or excessive.

    Completeness4/5

    The tool surface covers the core lifecycle well: scanning, checking, SBOM generation, compliance, policy evaluation, remediation, and threat intel. Minor gaps exist, such as a dedicated tool to update threat intel or manage vulnerability exceptions, but these are not critical to the primary workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources