Agents Index

KernelScan

Online

Linux kernel CVE analyzer: upload a .config, get a CycloneDX VEX report of affecting CVEs.

Visit publisherConnectJSON

What it can do: 11 tools

  • search_cvesSearch Linux kernel CVEs. No API key required: keyless callers get the free public tier — recent high-severity Linux kernel CVEs (capped at 25 results). Free *keyed* callers see only CVEs publish
  • get_cveFetch a single Linux kernel CVE by ID (e.g. ``CVE-2024-12345``). No API key required: keyless callers get the public representation of a CVE, but only for CVEs in the public set (recent high-severity); a
  • list_productsList the calling user's products with denormalized analysis stats. Paid plans only (basic / pro / enterprise). Free callers get a clear upgrade message.
  • get_productFetch one product owned by the caller, including the CVE breakdown. Returns 404 (not 403) if the product belongs to another user, so product existence isn't leaked across accounts.
  • get_product_vexReturn the VEX MANIFEST for one of the caller's products — metadata, not the document. Multi-megabyte CycloneDX documents (up to 8,000+ vulnerability entries) are not safe model-context payloads,
  • list_product_vex_entriesPage through the VEX vulnerability entries of one of the caller's products. Returns COMPLETE CycloneDX vulnerability objects for one bounded page — never the root document, never all entries — plus ``ret
  • create_productCreate a new product, run analysis, and return its initial stats. ``config_upload_id`` references a previously-staged .config that the caller POSTed to ``/api/configs/uploads`` over plain HTTP — the LLM
  • update_productUpdate a product owned by the caller. Re-runs analysis if the kernel_version, arch, or referenced .config changed. To change the .config, first POST the new file to ``/api/configs/uploads`` (see
  • whoamiReturn the caller's identity, plan, and quota state. Works without an API key: keyless callers get a lightweight public-tier payload (no account) describing how to request access.
  • request_accessExplain how to get a KernelScan account (no API key needed). Self-registration is open — there is no invitation to wait for and no admin in the loop. The user signs up on kernelscan.io themselves (email
  • submit_support_reportSend a support / dispute report to KernelScan staff. Use this when an automated CVE or factor assessment looks wrong, or when you need to hand human-needed context back to the team. The caller's

Connect it

Claude Code
claude mcp add --transport http kernelscan https://kernelscan.io/mcp/
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://kernelscan.io/mcp/
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "kernelscan": {
      "url": "https://kernelscan.io/mcp/"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "kernelscan": {
      "type": "http",
      "url": "https://kernelscan.io/mcp/"
    }
  }
}

Questions

What does KernelScan do?

Linux kernel CVE analyzer: upload a .config, get a CycloneDX VEX report of affecting CVEs. It exposes 11 tools to AI assistants.

What tools does KernelScan provide?

11 tools, including search_cves, get_cve, list_products, get_product, get_product_vex, list_product_vex_entries, create_product, update_product, whoami, request_access, submit_support_report.

How do I connect KernelScan to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://kernelscan.io/mcp/ as a custom connector or MCP server. Copy-paste setup is on this page.

Does KernelScan require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is KernelScan online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes KernelScan?

kernelscan.io. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Developer Tools