# BRAINIAC Cybersecurity Intelligence [Health: Active]

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

## Description
Cybersecurity Intelligence: 8 pay-per-call MCP tools for agents (x402 USDC on Base, no API key). Cybersecurity Intelligence tools for AI agents: get vulnerability details; check package vulnerabilities; batch check package vulnerabilities; assess vulnerability risk; get dependency tree; get package project health; and 2 more.

## Tools
Capabilities this server exposes over MCP:

- **cybersecurity-intelligence_vulnerability** — Look up a CVE or vulnerability ID before you install or deploy a dependency. Call with cveId (for example CVE-2021-44228). Returns aliases, summary, affected packages and ranges, CVSS score and severity, FIRST EPSS probability and percentile, and CISA KEV status including required action, due date, and ransomware campaign use. Sources merged from OSV, CISA KEV, FIRST EPSS, and NVD (each with its own source status). HTTP 200 with status complete, partial, or failed is charged in full. Keywords: CVE lookup, CISA KEV, FIRST EPSS, OSV, CVSS, known exploited, ransomware, affected packages, dependency risk, vulnerability ID, before you deploy, package security, advisory, KEV due date.
- **cybersecurity-intelligence_package-check** — Check one package and version for vulnerabilities using OSV, enriched with CISA KEV, EPSS, and NVD data before you install or deploy. Call with ecosystem, package, and version. Returns package, vulnerabilities, and source (package includes ecosystem, name, version). Sources: CISA KEV, OSV, and NVD. 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, CISA KEV, known exploited, KEV catalog, FIRST EPSS, exploit probability, OSV.
- **cybersecurity-intelligence_package-batch-check** — Check multiple packages and versions for vulnerabilities using OSV batch query, enriched with CISA KEV, EPSS, and NVD data before you install or deploy. Returns results and source (results includes package, vulnerabilities, source). Sources: CISA KEV, OSV, and NVD. For exact SBOM version matching, KEV gates, malicious-package advisories, and licence policy use software-security. 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, CISA KEV, known exploited, KEV catalog, FIRST EPSS, exploit probability, OSV.
- **cybersecurity-intelligence_risk-assess** — Produce a consolidated vulnerability risk assessment for multiple packages, combining OSV, CISA KEV, EPSS, and NVD data before you install or deploy. Returns assessment and source (assessment includes overallRisk, totalVulnerabilities, criticalCount, highCount, mediumCount, lowCount, kevCount, highEpssCount). Sources: CISA KEV, OSV, and NVD. 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, CISA KEV, known exploited, KEV catalog, FIRST EPSS, exploit probability, OSV.
- **cybersecurity-intelligence_dependency-tree** — Return direct and transitive dependencies, dependency versions and available dependency metadata using Google deps.dev API before you install or deploy. Call with ecosystem and packageName; optional version. Returns input and dependencyTree (input includes ecosystem, packageName, version). 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, before you install or deploy, ecosystem, packageName, version, input, dependencyTree.
- **cybersecurity-intelligence_package-project-health** — Return project activity indicators, repository associations, package metadata and available security information using Google deps.dev API before you install or deploy. Call with ecosystem and packageName. Returns input and projectHealth (input includes ecosystem, packageName). For exact SBOM version matching, KEV gates, malicious-package advisories. 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, before you install or deploy, ecosystem, packageName, input, projectHealth, Get package project health.
- **cybersecurity-intelligence_repository-scorecard** — Retrieve the official OpenSSF Scorecard result for a GitHub, GitLab or other supported repository before you install or deploy. Returns repository and scorecard (scorecard includes score, checks). For exact SBOM version matching, KEV gates, malicious-package advisories, and licence policy use software-security. 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, OpenSSF Scorecard, before you install or deploy, repository, Get repository Scorecard.
- **cybersecurity-intelligence_lockfile-audit** — Parse supported package lockfiles, identify dependencies and versions, then combine deps.dev and existing OSV/CISA/EPSS/NVD findings before you install or deploy. Call with lockfileContent; optional ecosystem. Returns input, dependencies, and vulnerabilities (input includes lockfileContent, ecosystem). Sources: deps.dev, OSV, and NVD. 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, vuln lookup, advisory, CVSS, package audit, lockfile audit, dependency check, FIRST EPSS, exploit probability, National Vulnerability Database, NVD record, deps.dev, OSV.

## 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-cybersecurity-intelligence": {
    "url": "https://www.brainiac.software/mcp/cybersecurity-intelligence"
  }
}
```

## Documentation

## What BRAINIAC Cybersecurity Intelligence does

BRAINIAC Cybersecurity Intelligence exposes eight security-analysis tools over MCP. The tools cover individual vulnerability lookups, package and batch package checks, consolidated risk assessments, dependency trees, package project health, repository Scorecard results, and lockfile audits.

Its vulnerability-oriented tools combine data from multiple public sources. Depending on the operation, results can include OSV advisories, CISA Known Exploited Vulnerabilities status, FIRST EPSS probability and percentile, NVD records, CVSS details, affected version ranges, required remediation dates, and ransomware-campaign indicators. The service is intended for dependency decisions before installation or deployment.

## How it works

Clients connect to the hosted streamable HTTP endpoint:

`https://www.brainiac.software/mcp/cybersecurity-intelligence`

Calls are paid individually through x402 using USDC on Base. No API key is required. A successful HTTP 200 response is charged at the full listed price even when the tool reports a `complete`, `partial`, or `failed` result. HTTP 4xx and 5xx responses are not charged for the package-check, batch-check, risk-assessment, dependency-tree, project-health, repository-scorecard, and lockfile-audit tools.

Inputs are tool-specific. Vulnerability lookup accepts a CVE or other vulnerability identifier. Package checks accept an ecosystem, package name, and version, while batch checks and risk assessments operate across multiple packages. Dependency and project-health queries use an ecosystem and package name, with an optional version for dependency trees. Lockfile auditing accepts lockfile content and an optional ecosystem.

## Setup and configuration

Configure an MCP client to use the hosted endpoint above. The service does not require an API key or server-side environment variables. Payment support for x402 and access to USDC on Base are required for paid calls.

The endpoint is suitable for clients that support remote streamable HTTP MCP connections. Exact client configuration depends on the MCP client being used.

## Tools and capabilities

- `cybersecurity-intelligence_vulnerability` looks up a CVE or vulnerability ID and returns aliases, summaries, affected packages and ranges, CVSS, EPSS, and CISA KEV information.
- `cybersecurity-intelligence_package-check` checks one package version for known vulnerabilities.
- `cybersecurity-intelligence_package-batch-check` checks multiple package versions using an OSV batch query and enrichment sources.
- `cybersecurity-intelligence_risk-assess` summarizes package exposure with overall risk and counts by severity, KEV status, and high EPSS findings.
- `cybersecurity-intelligence_dependency-tree` retrieves direct and transitive dependency information from Google deps.dev.
- `cybersecurity-intelligence_package-project-health` returns package activity indicators, repository associations, metadata, and available security information.
- `cybersecurity-intelligence_repository-scorecard` retrieves OpenSSF Scorecard results for supported GitHub, GitLab, and other repositories.
- `cybersecurity-intelligence_lockfile-audit` parses supported lockfiles and combines dependency data with OSV, CISA KEV, EPSS, and NVD findings.

## Limitations and notes

Results may be marked complete, partial, or failed while still producing an HTTP 200 response; those responses are charged in full. The package and lockfile tools are designed for vulnerability and dependency analysis, not every type of software-supply-chain policy. Exact SBOM version matching, malicious-package advisories, KEV gates, and license policy are identified as use cases for a separate `software-security` service.

_Full upstream README: https://allmcps.com/mcp/brainiac-cybersecurity-intelligence/readme_

