Developer · Remote MCP server
KernelScan
Linux kernel CVE analyzer: upload a.config, get a CycloneDX VEX report of affecting CVEs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.kernelscan/kernelscan- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-20
- Updated
- 2026-06-20
- Publisher
- io.kernelscan
- Namespace
- Namespace verified by the MCP Registry via the domain kernelscan.io · how
- Website
- kernelscan.io
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://kernelscan.io/mcp/ | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- KernelScan 1.26.0 · protocol 2025-06-18
- Tools discovered
- 11:
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 - Checked on
- 2026-10-05
How to connect KernelScan
KernelScan is a remote MCP server: there is nothing to install. Its endpoint is https://kernelscan.io/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Kenwea NotarySigned third-party verdict on what an npm package or file does when run. No key, no signup. | Remote · HTTPLive check: ✓ handshake |
| KeployEnd-to-end API testing - generate and run tests from OpenAPI, curl, Postman, or real user traffic. | Remote · HTTPLive check: ✓ handshake |
| KEPTA - the memory for AI systemsLocal encrypted memory for AI: hybrid search, 8 MCP tools, one file you own. Free, no cloud. | Local · stdio |
| Kernel MCP ServerAccess Kernel's cloud-based browsers and app actions via MCP (remote HTTP + OAuth). | Remote · HTTPLive check: sign-in required |
| KevscopeCVE patch-priority API + MCP: CISA KEV, EPSS, CVSS, SSVC. Keys $19/mo; 200 free calls/day. | Remote · HTTPLive check: ✓ handshake |
| KeyblindEncrypted secrets vault for AI agents - secrets resolved at runtime, never seen by LLMs. | Local · stdio |
| keyboardcrumbs.comLive threat intel for Claude - CVE, KEV predictions, IP lookup, malware hashes. Free, no API key. | Local · stdio |
| KeymemAssociative key-graph memory for LLM agents - recall by association, not vector similarity. | Local · stdio |