# BRAINIAC Software Supply Chain Security [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://www.brainiac.software/mcp/software-security  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/brainiac-software-supply-chain-security

## Description
Software Supply Chain Security: 6 pay-per-call MCP tools for agents (x402 USDC on Base, no API key). Software Supply Chain Security tools for AI agents: match SBOM vulnerabilities; report dependency risk; check KEV exposure; check licence compatibility; check malicious dependencies; precheck release security.

## Tools
Capabilities this server exposes over MCP:

- **software-security_sbom-vulnerability-match** — Parse a CycloneDX or SPDX SBOM, or a component list, and classify each exact package version against OSV advisories as affected, unaffected, or unknown before you install, merge, or release. A similar package name is not a match. Call with optional sbom, components. Returns truncated, approvesRelease, components, and warnings. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: CVE lookup, vulnerability ID, security advisory, package audit, lockfile audit, dependency check, CycloneDX, SPDX, software bill of materials, before you install, merge, or release, components, truncated, approvesRelease, warnings, Match SBOM vulnerabilities.
- **software-security_dependency-risk-report** — Summarise affected, unaffected, and unknown OSV advisory counts for each exact dependency version before you install, merge, or release. No risk score is calculated. Call with optional sbom, components. Returns truncated, approvesRelease, components, and warnings (components includes ecosystem, name, version, purl, problem, versionState, affectedCount, unaffectedCount). HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: CVE lookup, vulnerability ID, security advisory, package audit, lockfile audit, dependency check, CycloneDX, SPDX, software bill of materials, before you install, merge, or release, components, truncated, approvesRelease, warnings, Report dependency risk.
- **software-security_kev-exposure-check** — Compare exact dependency versions with OSV advisories and the CISA Known Exploited Vulnerabilities catalog before you install, merge, or release. A KEV entry is reported only when that CVE applies to the same package and version range. Call with optional sbom, components. Returns truncated, approvesRelease, catalogVersion, catalogReleasedAt, exposures. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: CVE lookup, vulnerability ID, security advisory, package audit, lockfile audit, dependency check, CycloneDX, SPDX, software bill of materials, CISA KEV, known exploited, KEV catalog, before you install, merge, or release, components, truncated.
- **software-security_license-compatibility-check** — Read licence identifiers declared in the SBOM or published by npm, PyPI, crates.io, or RubyGems, then compare them with the caller allow and deny policy before you install, merge, or release. Missing identifiers are not treated as compatible. Call with optional sbom, components, policy. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: CVE lookup, vulnerability ID, security advisory, package audit, lockfile audit, dependency check, CycloneDX, SPDX, software bill of materials, before you install, merge, or release, components, policy, truncated, approvesRelease, warnings.
- **software-security_malicious-dependency-check** — Look for OSV malicious-package advisories and npm compromise heuristics (typosquat distance to popular names, very new packages, few versions, missing repository) before you install, merge, or release. Signals are not proof of malware; no advisory does not mean the package is safe. Call with optional sbom, components. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: CVE lookup, vulnerability ID, security advisory, package audit, lockfile audit, dependency check, CycloneDX, SPDX, software bill of materials, before you install, merge, or release, components, truncated, approvesRelease, warnings, Check malicious dependencies.
- **software-security_release-precheck** — Combine exact-version OSV matches, CISA KEV exposure, licence policy, and malicious-package advisories into one release report before you install, merge, or release. The report never approves a release. Call with optional sbom, components, policy. Returns truncated, approvesRelease, assessment, components, warnings, and guidance. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: CVE lookup, vulnerability ID, security advisory, package audit, lockfile audit, dependency check, CycloneDX, SPDX, software bill of materials, CISA KEV, known exploited, KEV catalog, before you install, merge, or release, components, policy.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "brainiac-software-supply-chain-security": {
    "url": "https://www.brainiac.software/mcp/software-security"
  }
}
```

## Documentation

## What BRAINIAC Software Supply Chain Security does

BRAINIAC Software Supply Chain Security exposes six MCP tools for software supply-chain review. They analyze CycloneDX or SPDX software bills of materials, or supplied component lists, before dependencies are installed, changes are merged, or releases are prepared.

The checks focus on exact package names and versions. Vulnerability matching uses OSV advisories, while the KEV check also compares applicable vulnerabilities with the CISA Known Exploited Vulnerabilities catalog. Licence review applies caller-supplied allow and deny rules. Malicious-dependency analysis combines OSV malicious-package advisories with npm signals such as typosquat distance, package age, version count, and repository presence.

## How it works

Clients connect to the hosted MCP endpoint at `https://www.brainiac.software/mcp/software-security`. Calls are pay-per-call using x402 USDC on Base, with no API key required. A successful HTTP response with a complete, partial, or failed processing status is charged at the listed price; HTTP 4xx and 5xx responses are not charged.

Most tools accept optional `sbom` and `components` inputs. The licence and release tools also accept `policy`. Results can include truncation and warnings. Depending on the tool, responses identify affected, unaffected, or unknown components, report approval-related fields, provide catalog metadata, or return assessment and guidance.

## Tools and capabilities

- `software-security_sbom-vulnerability-match` classifies each exact component version against OSV advisories as affected, unaffected, or unknown.
- `software-security_dependency-risk-report` summarizes OSV result counts per dependency without calculating a risk score.
- `software-security_kev-exposure-check` identifies exact-version matches that are also represented in the CISA KEV catalog.
- `software-security_license-compatibility-check` reads licence identifiers from the SBOM or package registries and evaluates them against an allow/deny policy. Supported registry sources include npm, PyPI, crates.io, and RubyGems.
- `software-security_malicious-dependency-check` reports OSV malicious-package advisories and npm compromise heuristics.
- `software-security_release-precheck` combines OSV, KEV, licence, and malicious-package results into one release report.

## Limitations and notes

Exact matching matters: a similar package name is not treated as the same component, and a KEV exposure is reported only when the CVE applies to the same package and version range. Missing licence identifiers are not considered compatible.

Malicious-package signals are indicators rather than proof of malware, and the absence of an advisory does not establish that a package is safe. The release precheck reports an assessment but never approves a release. Dependency results can contain unknown states, and responses may be truncated. A status of complete, partial, or failed in an HTTP 200 response remains billable at the full listed price.

_Full upstream README: https://allmcps.com/mcp/brainiac-software-supply-chain-security/readme_

