Known Vulnerabilities Lookup

Find reported vulnerabilities for a package version in OSV. Returns vulnerability identifiers, available severity and affected or fixed versions.

Pay by wallet (x402) cve-lookup

Example

Example answer
{
  "version": "test_value",
  "ecosystem": "npm",
  "package_name": "test_value",
  "recommendation": "No known vulnerabilities for this version.",
  "vulnerabilities": [],
  "highest_severity": "none",
  "total_vulnerabilities": 0
}

Inputs

FieldTypeRequiredWhat it is
versionstringYes—
ecosystemstringNonpm/pypi/maven/go/cargo/nuget
package_namestringYes—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
recommendationstringAlways (present in every successful answer)
vulnerabilitiesarrayAlways (present in every successful answer)
highest_severitystringAlways (present in every successful answer)
total_vulnerabilitiesintegerAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "cve-lookup",
    "inputs": {
      "version": "4.17.20",
      "package_name": "lodash"
    },
    "max_price_cents": 5
  }'

Limitations

  • New vulnerabilities and updated scores can lag

    Uses OSV database — newly published CVEs may take hours to appear and severity scores may be updated after initial publication

    What to do instead: For zero-day awareness, supplement with the NVD RSS feed and vendor security advisories