Skip to main content
Glama
koda-ai-studio

agent-bom

by koda-ai-studio
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
      B
      maintenance
      Security scanner for MCP servers. Detects prompt injection, command injection, auth bypass, and excessive permissions across tools, resources, and prompts.
      46 npm
      2
      MIT

    • MCP Shield

      rob925
      A
      license
      C
      quality
      D
      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

    • agent-crashtest

      glibey
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.
      78 npm
      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
      30 PyPI
      2
      Apache 2.0
    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

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target distinct operations: scan (full audit), check (single package CVE), generate_sbom (SBOM export), policy_check, remediate, compliance, intel_lookup, exposure_paths. However, scan and generate_sbom both 'discover agents and extract dependencies', and policy_check/remediate internally run scans, creating mild overlap in scope. Descriptions do help distinguish them, keeping ambiguity low.

    Naming Consistency3/5

    Mix of verb_noun (generate_sbom, intel_lookup, policy_check, exposure_paths) and bare nouns/verbs (scan, check, compliance, remediate). Consistent snake_case style throughout keeps it readable, but the verb-vs-noun convention is not uniform.

    Tool Count5/5

    Eight tools is well within the ideal 3-15 range for a security scanning server. Each tool covers a distinct stage of the security workflow (scan, check, SBOM, policy, remediation, compliance, intel, attack paths), so each earns its place.

    Completeness4/5

    The surface covers the full security lifecycle: scanning, SBOM generation, CVE lookup, policy gating, remediation, compliance, and attack-path analysis. Minor gaps exist—no tools for managing/saving policies, comparing baseline scans, or suppressing/waiving findings—but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources