circl_vuln_search

Pack: circl-vulnerability-lookup · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/circl_vuln_search for the schema, then POST the same URL with its arguments for the data.

“Vulnerabilities in [vendor] [product]” / “CVEs affecting Apache log4j” / “known issues in [software]” — search CIRCL Vulnerability-Lookup for every vulnerability recorded against a vendor/product pair. Use for software inventory triage (“what is known against the version we run”), dependency review, and vendor risk assessment. Vendor and product are matched against the CPE vendor/product strings, so use the CPE spelling (“apache” + “log4j”, “microsoft” + “windows_10”), not a marketing name.

Parameters

NameTypeRequiredDescription
vendorstringyesCPE vendor string, e.g. “apache”, “microsoft”, “cisco”.
productstringyesCPE product string, e.g. “log4j”, “windows_10”, “ios”.
limitnumbernoMaximum records to return, 1-100. Default 25.

Example call

Arguments

{
  "vendor": "apache",
  "product": "log4j",
  "limit": 2
}

curl

curl -X POST https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"circl_vuln_search","arguments":{"vendor":"apache","product":"log4j","limit":2}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('circl_vuln_search', {
  "vendor": "apache",
  "product": "log4j",
  "limit": 2
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the circl-vulnerability-lookup pack
{
  "mcpServers": {
    "circl-vulnerability-lookup": {
      "url": "https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 27, 2026