Skip to content

BRAINIAC Software Supply Chain Security MCP server

software.brainiac/software-securitybrainiac.softwarestreamable-httpv1.0.1Scanned

Paid Software Supply Chain Security API via x402. Unpaid tool calls return 402.

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BRAINIAC Software Supply Chain Security MCP server can do

The BRAINIAC Software Supply Chain Security MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: software-security_sbom-vulnerability-match, software-security_malicious-dependency-check and software-security_release-precheck), but cannot delete data. 3 tools only read.

6 tools bring in text other people can write (software-security_sbom-vulnerability-match, software-security_dependency-risk-report, software-security_kev-exposure-check and 3 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • software-security_malicious-dependency-checkLook for OSV malicious-package advisories and npm compromise heuristics (typosquat distance to popular names, very new packages, few versions, missing repository).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Look for OSV malicious-package advisories and npm compromise heuristics (typosquat distance to popular names, very new packages, few versions, missing repository). Signals are not proof of malware; no advisory does not mean the package is safe. Price $0.06 USDC. POST /api/v1/software-security/malicious-dependency-check. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Check malicious dependencies
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • software-security_release-precheckCombine exact-version OSV matches, CISA KEV exposure, licence policy, and malicious-package advisories into one release report.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Combine exact-version OSV matches, CISA KEV exposure, licence policy, and malicious-package advisories into one release report. The report never approves a release. Price $0.15 USDC. POST /api/v1/software-security/release-precheck. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Precheck release security
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • software-security_sbom-vulnerability-matchParse a CycloneDX or SPDX SBOM, or a component list, and classify each exact package version against OSV advisories as affected, unaffected, or unknown.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Parse a CycloneDX or SPDX SBOM, or a component list, and classify each exact package version against OSV advisories as affected, unaffected, or unknown. A similar package name is not a match. Price $0.08 USDC. POST /api/v1/software-security/sbom-vulnerability-match. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Match SBOM vulnerabilities
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • software-security_dependency-risk-reportSummarise affected, unaffected, and unknown OSV advisory counts for each exact dependency version.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "summarise": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Summarise affected, unaffected, and unknown OSV advisory counts for each exact dependency version. No risk score is calculated. Price $0.08 USDC. POST /api/v1/software-security/dependency-risk-report. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Report dependency risk
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • software-security_kev-exposure-checkCompare exact dependency versions with OSV advisories and the CISA Known Exploited Vulnerabilities catalog.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check KEV exposure
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • software-security_license-compatibility-checkRead 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.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Missing identifiers are not treated as compatible. Price $0.05 USDC. POST /api/v1/software-security/license-compatibility-check. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Check licence compatibility
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.brainiac.software/mcp/software-security: tools/list returned 6 tools to an anonymous client, including software-security_sbom-vulnerability-match (write), software-security_malicious-dependency-check (write), software-security_release-precheck (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http software-security https://www.brainiac.software/mcp/software-security
claude mcp add --transport http software-security https://www.brainiac.software/mcp/software-security

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__software-security__software-security_dependency-risk-report",
      "mcp__software-security__software-security_kev-exposure-check",
      "mcp__software-security__software-security_license-compatibility-check"
    ],
    "ask": [
      "mcp__software-security__software-security_sbom-vulnerability-match",
      "mcp__software-security__software-security_malicious-dependency-check",
      "mcp__software-security__software-security_release-precheck"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as software-security. Review it before you use it.

Capability tags behind 6 rules
  • mcp__software-security__software-security_sbom-vulnerability-match untrusted-input
  • mcp__software-security__software-security_dependency-risk-report untrusted-input
  • mcp__software-security__software-security_kev-exposure-check untrusted-input
  • mcp__software-security__software-security_license-compatibility-check untrusted-input
  • mcp__software-security__software-security_malicious-dependency-check untrusted-input
  • mcp__software-security__software-security_release-precheck untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/software.brainiac/software-security/verify?hash=4075d151d77ddeab4dfb14eedb1d2216b74a98a552c3f67319e8b9d57392736a" | jq -e '.changed == false'

Pinned hash 4075d151d77d, from Nov 20, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/software.brainiac/software-security/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for software.brainiac/software-security
[![Anlyon Radar](https://radar.anlyon.com/badge/software.brainiac/software-security.svg)](https://radar.anlyon.com/servers/software.brainiac/software-security)

Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.

BRAINIAC Software Supply Chain Security MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BRAINIAC Software Supply Chain Security MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BRAINIAC Software Supply Chain Security MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BRAINIAC Software Supply Chain Security MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BRAINIAC Software Supply Chain Security MCP server have?

6 tools: 3 write, 3 read. software-security_sbom-vulnerability-match, software-security_malicious-dependency-check, software-security_release-precheck, software-security_dependency-risk-report, software-security_kev-exposure-check and software-security_license-compatibility-check.

Does the BRAINIAC Software Supply Chain Security MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BRAINIAC Software Supply Chain Security MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BRAINIAC Software Supply Chain Security MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.