Connect KernelScan and your agent gets 11 tools, among them create_product, get_cve, get_product. It answers at https://kernelscan.io/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Linux kernel CVE analyzer: upload a .config, get a CycloneDX VEX report of affecting CVEs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_product | Create 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 does NOT emit the config text itself Inputs: name, kernel_version, arch, config_upload_id, description, factor_ids |
get_cve | Fetch 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); any other id returns ``not found``. Fr Inputs: cve_id |
get_product | Fetch 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. Inputs: product_id |
get_product_vex | Return 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, so this tool returns a bounded manifest: Cyc Inputs: product_id |
list_product_vex_entries | Page 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 ``returned``, ``total_matching``, and a `` Inputs: product_id, statuses, severities, kev, exploit_maturity, cve_ids |
list_products | List the calling user's products with denormalized analysis stats. Paid plans only (basic / pro / enterprise). Free callers get a clear upgrade message. |
request_access | Explain 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 + password, accepting the terms), con Inputs: email, name, reason |
search_cves | Search 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 published in the last 60 days; basic+ keyed callers Inputs: query, severity, cvss_min, published_after, limit |
submit_support_report | Send 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 API-key user is attached automatically (id, e Inputs: category, subject, message, cve_id, product_id, assessment_id |
update_product | Update 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 ``create_product`` for the curl recipe) and p Inputs: product_id, name, description, kernel_version, arch, config_upload_id |
whoami | Return 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. |
Every block below points at https://kernelscan.io/mcp/. Pick your client and copy.
claude mcp add --transport http kernelscan https://kernelscan.io/mcp/
{
"mcpServers": {
"kernelscan": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://kernelscan.io/mcp/"]
}
}
}{
"mcpServers": {
"kernelscan": {
"url": "https://kernelscan.io/mcp/"
}
}
}{
"servers": {
"kernelscan": {
"type": "http",
"url": "https://kernelscan.io/mcp/"
}
}
}{
"context_servers": {
"kernelscan": {
"url": "https://kernelscan.io/mcp/"
}
}
}{
"mcpServers": {
"kernelscan": {
"serverUrl": "https://kernelscan.io/mcp/"
}
}
}{
"mcpServers": {
"kernelscan": {
"url": "https://kernelscan.io/mcp/"
}
}
}name: KernelScan
version: 0.0.1
schema: v1
mcpServers:
- name: KernelScan
type: streamable-http
url: https://kernelscan.io/mcp/{
"mcpServers": {
"kernelscan": {
"httpUrl": "https://kernelscan.io/mcp/"
}
}
}{
"mcpServers": {
"kernelscan": {
"type": "http",
"url": "https://kernelscan.io/mcp/"
}
}
}{
"mcpServers": {
"kernelscan": {
"url": "https://kernelscan.io/mcp/"
}
}
}goose://extension?url=https%3A%2F%2Fkernelscan.io%2Fmcp%2F&type=streamable_http&id=kernelscan&name=KernelScan
It answered our last check on 24 October 2026 in 71 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by kernelscan.io and served from kernelscan.io, the vendor's own domain: https://kernelscan.io/mcp/.
11, as returned by the server's own tools/list on 22 September 2026: create_product, get_cve, get_product, get_product_vex, list_product_vex_entries, list_products, request_access, search_cves, and 3 more.
It answered our last check on 24 October 2026 in 71 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://kernelscan.io/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.kernelscan. Endpoint host: kernelscan.io. ARD identifier: urn:air:io.kernelscan:mcp:kernelscan.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.