Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
scanA

Run a full AI supply chain security scan and return an AI-BOM.

    Point it at a target with one of:
      • repo_url     — a public git repo URL (cloned + scanned, no checkout)
      • config_path  — a local project / MCP-config directory
      • image        — a Docker image
      • sbom_path    — an existing CycloneDX/SPDX SBOM
      • package      — a single package or MCP launch command (pair it with
                       ``ecosystem`` when the spec names no launcher)
    With none of these, it auto-discovers local MCP clients (Claude Desktop,
    Cursor, Windsurf, VS Code Copilot, OpenClaw, etc.).

    It extracts package dependencies, queries OSV.dev for CVEs, assesses
    config security (credential exposure, tool access), computes blast
    radius, and returns structured results. Scanning is fully static and
    read-only — repository and image contents are parsed, never executed.

    Returns:
        JSON with the complete AI-BOM report including agents, packages,
        vulnerabilities, blast radius, and remediation guidance.
    
checkA

Check a specific package for known CVEs before installing.

    Queries OSV.dev for vulnerabilities in the given package. Use this
    before installing an MCP server or dependency to verify it is safe.

    Args:
        package: Package name with optional version, e.g. "express@4.18.2",
                 "@modelcontextprotocol/server-filesystem@2025.1.14",
                 or just "requests" (resolves @latest).
        ecosystem: Package ecosystem — "npm", "pypi", "go", "cargo",
                   "maven", "nuget", "rubygems", "composer", "swift",
                   "pub", "hex", "conda", "deb", "apk", or "rpm".
                   Defaults to "npm".

    Returns:
        JSON with package, version, ecosystem, vulnerability count,
        and vulnerability details (id, severity, cvss, fix version, summary).
    
intel_lookupA

Look up one advisory from the local threat-intel database.

exposure_pathsA

Return ranked ExposurePath JSON for headless security agents.

    This is the agent-native graph surface: Claude, Cursor, Codex,
    Windsurf, Cortex, and other MCP clients can request the same
    investigation objects used by the dashboard without scraping UI state.
    
policy_checkA

Evaluate a security policy against current scan results.

    Runs a scan, then evaluates the provided policy rules against the
    findings. Policies can gate on severity thresholds, CISA KEV status,
    AI risk flags, credential exposure, and denied packages.

    Args:
        policy_json: JSON string containing policy rules. Example:
            {"rules": [{"id": "no-critical", "severity_gte": "critical",
            "action": "fail"}, {"id": "no-kev", "kev": true, "action": "fail"}]}

    Returns:
        JSON with passed (bool), violations list, failure_count, and
        warning_count.
    
generate_sbomA

Generate a Software Bill of Materials (SBOM) for your AI agent setup.

    Discovers AI agents and MCP servers, extracts all package dependencies,
    and generates a standards-compliant SBOM.

    Args:
        format: SBOM format — "cyclonedx" (CycloneDX 1.7) or "spdx" (SPDX 3.0).
        config_path: Path to a specific MCP config directory.
                     If not provided, auto-discovers all local agent configs.

    Returns:
        JSON string containing the SBOM in the requested format.
    
complianceA

Get OWASP LLM Top 10 / OWASP MCP Top 10 / MITRE ATLAS / NIST AI RMF compliance posture.

    Scans local MCP configurations, maps findings to 47 security controls
    across four AI security frameworks, and returns per-control
    pass/warning/fail status with an overall compliance score.

    Args:
        config_path: Path to a specific MCP config directory.
                     If not provided, auto-discovers all local agent configs.
        image: Docker image reference to scan (e.g. "nginx:1.25").

    Returns:
        JSON with overall_score (0-100), overall_status (pass/warning/fail/no_data),
        and per-control details for OWASP LLM Top 10 (10 controls),
        OWASP MCP Top 10 (10 controls), MITRE ATLAS (13 techniques),
        and NIST AI RMF (14 subcategories). Plus a nist_800_53_catalog line:
        the vendor-asserted, catalog-backed NIST SP 800-53 Rev 5 score over
        evaluated controls only (with ISO-27001-by-id attribution), scored
        independently and NOT folded into overall_score.
    
remediateA

Generate a remediation plan for vulnerabilities in your AI agent setup.

    Scans for vulnerabilities, then generates actionable fix commands for
    each affected package (npm install, pip install), credential scope
    reduction guidance, and reports on unfixable vulnerabilities.

    Args:
        config_path: Path to a specific MCP config directory.
                     If not provided, auto-discovers all local agent configs.
        image: Docker image reference to scan (e.g. "nginx:1.25").

    Returns:
        JSON with package_fixes (upgrade commands by ecosystem),
        credential_fixes (scope reduction steps), and unfixable items.
    

Prompts

Interactive templates invoked by user choice

NameDescription
quick-auditRun a complete security audit of your AI agent setup
pre-install-checkCheck an MCP server package for vulnerabilities before installing
remediation-planDraft a human-reviewed remediation plan without modifying files

Resources

Contextual data attached and managed by the client

NameDescription
profiles_resourceTask profiles and startup commands; no tool schemas or credentials
policy_template_resourceGet a default security policy template for agent-bom. Returns a ready-to-use policy with common rules: block critical CVEs, flag CISA KEV entries, warn on unverified servers, and limit credential exposure.
tool_metrics_resourceReturn bounded MCP tool execution metrics for observability.
framework_controls_resourceSummarize framework coverage and the evidence surfaces behind each claim.

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