# KernelScan (remote · kernelscan.io)

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

- Trust score: 64/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `kernelscan.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-kernelscan-kernelscan/kernelscan.md), [page](https://verifymcp.io/servers/io-kernelscan-kernelscan/kernelscan)

## Channel facts

- Endpoint: `https://kernelscan.io/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1676 tokens (~167/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (10% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-kernelscan-kernelscan https://kernelscan.io/mcp/
```

### Codex

```toml
[mcp_servers.io-kernelscan-kernelscan]
url = "https://kernelscan.io/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-kernelscan-kernelscan": {
      "type": "remote",
      "url": "https://kernelscan.io/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-kernelscan-kernelscan --url https://kernelscan.io/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-kernelscan-kernelscan:
    url: "https://kernelscan.io/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "io-kernelscan-kernelscan": {
      "type": "http",
      "url": "https://kernelscan.io/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (10)

### `search_cves` (~201 tokens)

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 get the full corpus.
        ``query`` matches against CVE id and description (case-insensitive).
        ``severity`` filters by effective severity (``critical``/``high``/``medium``/``low``).
        ``cvss_min`` filters by effective CVSS score.
        ``published_after`` (ISO 8601) returns only CVEs newer than that date.
        Returns up to ``limit`` (max 100) CVEs, newest first.

Input parameters:

- `cvss_min`
- `limit` (integer)
- `published_after`
- `query`
- `severity`

### `get_cve` (~146 tokens)

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``. Free *keyed* callers get a 404 for CVEs
        published more than 60 days ago. AI risk-summary / analysis fields are
        included for any keyed user on CVEs in the public set, and for pro /
        enterprise on every assessed CVE.

Input parameters:

- `cve_id` (string, required)

### `list_products` (~42 tokens)

List the calling user's products with denormalized analysis stats.

        Paid plans only (basic / pro / enterprise). Free callers get a clear
        upgrade message.

Output parameters:

- `result` (array)

### `get_product` (~58 tokens)

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.

Input parameters:

- `product_id` (string, required)

### `get_product_vex` (~78 tokens)

Return the CycloneDX 1.6 VEX document for one of the caller's products.

        Reads from the 24h ProductVexCache; if the cache is empty/expired the
        next call to ``get_product`` (or the REST endpoint) will regenerate it.

Input parameters:

- `product_id` (string, required)

### `create_product` (~301 tokens)

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 (a real kernel .config is
        ~100–200 KB and exceeds a single tool-call output budget). Workflow:

        1. Caller / wrapper script:
           ``curl -H "Authorization: Bearer ks_live_..." \
                  -F "config_file=@.config" \
                  https://kernelscan.io/api/configs/uploads``
           returns ``{config_upload_id, sha256, size_bytes, expires_at}``.
        2. Pass that ``config_upload_id`` into this tool.

        Uploads are per-user, single-use, and expire 30 minutes after upload.
        Same tier gates as POST /api/products: free can't create products at
        all, basic is capped at 3 products, pro at 10. ``factor_ids`` are
        silently ignored unless the tier allows security factors
        (``pro``/``enterprise``). Re-using a product name returns 409.

Input parameters:

- `arch` (string, required)
- `config_upload_id` (string, required)
- `description`
- `factor_ids`
- `kernel_version` (string, required)
- `name` (string, required)

### `update_product` (~172 tokens)

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 pass the returned ``config_upload_id`` here. Leave
        ``config_upload_id`` as ``None`` to keep the existing .config.
        ``factor_ids=None`` leaves factor selections untouched; an empty
        list clears them. Same tier gates as PUT /api/products/{id}.

Input parameters:

- `arch`
- `config_upload_id`
- `description`
- `factor_ids`
- `kernel_version`
- `name`
- `product_id` (string, required)

### `whoami` (~49 tokens)

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.

### `request_access` (~161 tokens)

Request an invitation to KernelScan from inside MCP (no API key needed).

        Use this when a keyless caller wants the full service. It records an
        invitation request and emails a confirmation; an admin reviews it and,
        if approved, sends an invitation code. This tool does NOT create an
        account or mint an API key — you finish signup (including accepting the
        terms) on the website after you receive the invitation.

        ``email`` is required. ``name`` and ``reason`` are optional context for
        the reviewer. The response is identical whether or not the email is
        already known, so it never reveals account state.

Input parameters:

- `email` (string, required)
- `name`
- `reason`

### `submit_support_report` (~220 tokens)

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, email, plan)
        so support can look the account up.

        ``category`` should be one of:
        - ``cve_assessment`` — wrong AI verdict / CVSS / CWE on a CVE
        - ``factor_assessment`` — wrong factor verdict for a product
        - ``bug`` — broken behavior in the API or UI
        - ``other`` — anything else

        ``cve_id`` / ``product_id`` / ``assessment_id`` are optional but
        recommended — they let support jump straight to the relevant row.

Input parameters:

- `assessment_id`
- `category` (string, required)
- `cve_id`
- `message` (string, required)
- `product_id`
- `subject` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-kernelscan-kernelscan/kernelscan#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://kernelscan.io/mcp/
- Website: https://kernelscan.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-kernelscan-kernelscan/kernelscan/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-kernelscan-kernelscan/kernelscan/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-kernelscan-kernelscan/kernelscan