Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KEVWire

REMOTE · KEVWIRE.COM

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

Available components

+3 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 593 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability check failed: schema churn in the 26 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 23% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 10 Nov 26 +1

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

  • 8 Nov 26 +1

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

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://kevwire.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kevwire.com CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 4a4f081b38f5b3c00e75b3b17c62a4dc
SANs: kevwire.com, staging.kevwire.com, *.staging.kevwire.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of kevwire.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kevwire.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000
content-security-policy default-src 'none'; script-src 'self'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; manifest-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kevwire.com/mcp Verified 200
http (plaintext) http://kevwire.com/mcp HTTPS enforced 301 https://kevwire.com/mcp
MCP tools · 5 exposed · ~538 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_record ~77

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

list_recent_exploited ~98

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.

NameTypeReqDescription
daysinteger––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

list_sources ~45

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_technologies ~68

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.

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

search_vulnerabilities ~250

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.

NameTypeReqDescription
kindstring––
known_exploited_onlyboolean–Only records in the CISA Known Exploited Vulnerabilities catalog.
limitinteger––
offsetinteger––
querystring–Words to match, e.g. "php rce", a CVE ID, a product, or an event name like "PHP2Shell".
sortstring––
technologiesarray–Technology labels, e.g. ["Microsoft Windows", "PHP"]. Matches any.

No output schema declared.

No examples provided.

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.

remote · kevwire.com

# add to Claude Code
claude mcp add --transport http com-kevwire-kevwire 'https://kevwire.com/mcp'
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.