# KEVWire (remote · kevwire.com)

Exploited vulnerabilities, critical CVEs, breaches and AI security incidents, with primary sources.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://kevwire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `6.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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 593 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability check failed: schema churn in the 26 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the KEVWire MCP server?

KEVWire is a hosted endpoint at https://kevwire.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-kevwire-kevwire 'https://kevwire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kevwire-kevwire": {
      "url": "https://kevwire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kevwire-kevwire": {
      "type": "http",
      "url": "https://kevwire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kevwire-kevwire]
url = "https://kevwire.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-kevwire-kevwire --url 'https://kevwire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kevwire-kevwire:
    url: "https://kevwire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kevwire-kevwire": {
      "Transport": "http",
      "Url": "https://kevwire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kevwire-kevwire -t streamable-http -u 'https://kevwire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kevwire-kevwire": {
      "type": "http",
      "url": "https://kevwire.com/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-11-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.

### 2026-11-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.

### 2026-11-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.

### 2026-11-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.

### 2026-11-12 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37.

### 2026-11-10 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30.

### 2026-11-08 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23.

### 2026-11-06 (score 71, +1)

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

## MCP tools (5)

### `search_vulnerabilities` (~250 tokens)

Search vulnerabilities, breaches, and advisories

Search the KEVWire corpus (CISA KEV, NVD high/critical CVEs, GitHub advisories, national CERTs, security reporting, editorial records) by words, technology, kind or exploitation. Use it to answer "is X affected" or "what is known about Y"; for a known ID use get_record, and for a plain "what is being exploited lately" list use list_recent_exploited. Default order is "urgent": the last 30 days first, then known exploitation, CVSS 9+, breaches. Results are paged (see hasMore and offset) and include source URLs to cite.

Input parameters:

- `kind` (string)
- `known_exploited_only` (boolean): Only records in the CISA Known Exploited Vulnerabilities catalog.
- `limit` (integer)
- `offset` (integer)
- `query` (string): Words to match, e.g. "php rce", a CVE ID, a product, or an event name like "PHP2Shell".
- `sort` (string)
- `technologies` (array): Technology labels, e.g. ["Microsoft Windows", "PHP"]. Matches any.

### `get_record` (~77 tokens)

Get one record with full evidence

Fetch one record by CVE ID, GHSA ID, or KEVWire record ID, with every source, measurement date, CISA deadline and a permalink. Any published CVE resolves, even outside the tracked set. Returns isError with a hint when nothing matches; then try search_vulnerabilities.

Input parameters:

- `id` (string, required)

### `list_recent_exploited` (~98 tokens)

Recently exploited vulnerabilities

Vulnerabilities with documented exploitation (CISA KEV or explicit reporting) published within the last N days, most urgent first. Use it for briefings such as "what was exploited this week"; to narrow by product or words, use search_vulnerabilities with known_exploited_only. Paged with offset and hasMore.

Input parameters:

- `days` (integer)
- `limit` (integer)
- `offset` (integer)

### `list_technologies` (~68 tokens)

List technology labels

Technology labels (vendors and products) usable in search_vulnerabilities' technologies filter, with how many records each covers, most covered first. Use it to find the exact label before filtering. Optionally filter by text.

Input parameters:

- `limit` (integer)
- `query` (string)

### `list_sources` (~45 tokens)

List data sources and their status

Every source KEVWire ingests, with scope, limitations, retrieval status, last success and record counts. Use it to describe coverage honestly or to explain why something may be missing.

## Diagnostics

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

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73
- 2026-11-09: 72
- 2026-11-08: 72
- 2026-11-07: 71
- 2026-11-06: 71
- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 64
- 2026-10-26: 64

## Common questions

### What is the KEVWire MCP server?

KEVWire is an MCP server listed in the public MCP registry as com.kevwire/kevwire. Exploited vulnerabilities, critical CVEs, breaches and AI security incidents, with primary sources. This page covers its hosted endpoint (https://kevwire.com/mcp).

### Is the KEVWire MCP server safe to use?

KEVWire scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the KEVWire MCP server expose?

KEVWire exposes 5 tools: search_vulnerabilities, get_record, list_recent_exploited, list_technologies, list_sources. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.

### Does the KEVWire MCP server require authentication?

No. We connected to KEVWire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the KEVWire MCP server still maintained?

KEVWire is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the KEVWire MCP server?

VerifyMCP ran 13 checks on KEVWire, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://kevwire.com/mcp
- Website: https://kevwire.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-kevwire-kevwire/kevwire.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kevwire-kevwire/kevwire/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-kevwire-kevwire/kevwire.json
- HTML version of this page: https://verifymcp.io/servers/com-kevwire-kevwire/kevwire
