Skip to main content
Glama
MCP-Mirror

MCP SBOM Server

by MCP-Mirror
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

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
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

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'scan' has a clear and distinct purpose: generating an SPDX SBOM for a container image using Trivy scanner.

Naming Consistency5/5

With only one tool, naming consistency is inherently perfect. The tool name 'scan' follows a simple verb pattern, and there are no other tools to compare it against for inconsistency.

Tool Count2/5

A single tool is too few for a server named 'MCP SBOM Server', which suggests a broader scope related to Software Bill of Materials. While the tool covers scanning, typical SBOM workflows might include operations like listing, analyzing, or comparing SBOMs, making this feel thin and incomplete.

Completeness2/5

The tool surface is severely incomplete for an SBOM domain. It only provides scanning functionality, with no tools for retrieving, updating, deleting, or analyzing SBOMs. This creates significant gaps that will likely cause agent failures in broader SBOM-related tasks.

Resources