Skip to main content
Glama

BRAINIAC Software Supply Chain Security

Check KEV exposure

software-security_kev-exposure-check
Read-onlyIdempotent

Compare exact dependency versions with OSV advisories and the CISA Known Exploited Vulnerabilities catalog. A KEV entry is reported only when that CVE applies to the same package and version range. Price $0.06 USDC. POST /api/v1/software-security/kev-exposure-check. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "software-security_kev-exposure-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sbomNosbom, string, length 2 to 400000. Optional.
componentsNocomponents, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
warningsNowarnings. Array.
exposuresNoexposures. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
catalogVersionNocatalogVersion. String.
approvesReleaseNoapprovesRelease. Boolean.
catalogReleasedAtNocatalogReleasedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, open-world, idempotent, non-destructive, so the description's real contribution is the payment flow: $0.06 USDC, POST endpoint, and that an unpaid call returns x402 terms without running. That is behavior an agent cannot learn from annotations. It also explains the matching rule (KEV reported only when the CVE applies to the same package and version range), which usefully narrows what a hit means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the matching semantics and followed by price, endpoint, and payment behavior. Every sentence carries information; the endpoint and price lines are operational metadata rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be explained. However, both inputs are optional with zero required parameters, and the description never says whether an sbom, components, or either one is needed for a meaningful call. For a tool whose only inputs are optional, that gap matters to correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both sbom and components. The description adds only the notion that versions are matched exactly against advisory ranges, not per-parameter guidance. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and two named resources: compare exact dependency versions against OSV advisories and the CISA KEV catalog. The 'exact dependency versions' phrasing hints at how it differs from the SBOM-matching sibling, but it never names that sibling or draws the line explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call it to learn whether a dependency is exposed to a known-exploited CVE. There is no explicit when-to-use versus software-security_sbom-vulnerability-match or software-security_malicious-dependency-check, and no stated prerequisites (e.g. needing version data rather than a raw SBOM).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources