Skip to main content
Glama

BRAINIAC Software Supply Chain Security

Check malicious dependencies

software-security_malicious-dependency-check
Read-onlyIdempotent

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.

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_malicious-dependency-check"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
warningsNowarnings. Array.
componentsNocomponents. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
approvesReleaseNoapprovesRelease. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description adds non-obvious behavior: price of $0.06 USDC, the endpoint, and critically that an unpaid call returns x402 payment terms without executing. It also pre-empts false-positive and false-negative readings of the output, which no annotation conveys.

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?

Front-loads what is checked, then caveats, then payment mechanics — a sensible order with little waste. The raw endpoint path and price line are transactional rather than descriptive but still serve the caller.

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

Completeness4/5

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

An output schema exists, so return values need not be described. With an output schema, a 4 is appropriate: the description tells the agent what is scanned, how to read signals, and how payment gating works — the main remaining gap is sibling differentiation.

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% for both sbom and components, so the schema already documents the inputs. The description adds no guidance on how sbom and components interact or which to supply, so it stays at baseline.

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

Purpose5/5

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

States a specific verb and resource: hunts OSV malicious-package advisories plus concrete npm compromise heuristics (typosquat distance, newness, version count, missing repository). That is specific enough to separate it from the sibling sbom-vulnerability-match and license-compatibility-check without opening any schema.

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?

Explains the interpretive frame well ('signals are not proof', 'no advisory does not mean the package is safe'), which implicitly tells the agent when the result is inconclusive. But it never says when to prefer this over dependency-risk-report or sbom-vulnerability-match, so routing is left to inference.

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