Skip to main content
Glama
gkhays

MCP SBOM Server

by gkhays
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
scanC
Execute Trivy scanner to generate SPDX SBOM for a container image.
Supports the SPDX JSON format.

Args:
    image (str): The container image name/reference to scan

Returns:
    str: Test response or error message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single 'scan' tool has a clearly defined purpose of generating SPDX SBOMs for container images using Trivy scanner.

Naming Consistency5/5

With a single tool, naming consistency is inherently perfect. The tool name 'scan' follows a clear verb-based naming pattern that accurately describes its function without any conflicting naming conventions to compare against.

Tool Count2/5

A single tool for an SBOM server feels insufficient for the apparent domain scope. While scanning is a core function, SBOM management typically involves additional operations like listing, retrieving, comparing, or validating SBOMs. The server appears to have significant functional gaps beyond the basic scan capability.

Completeness2/5

The tool surface is severely incomplete for an SBOM server. While scanning is essential, there are obvious gaps in the lifecycle: no tools for retrieving stored SBOMs, comparing different SBOM versions, validating SBOM formats, or managing SBOM metadata. This limited surface will likely cause agent failures when trying to perform comprehensive SBOM workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources