KEVWire

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://kevwire.com/mcp

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

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

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

https://kevwire.com/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• search_vulnerabilities

  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

• get_record

  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.

• list_recent_exploited

  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. Pag

• list_technologies

  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.

• list_sources

  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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (kevwire.com) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 996 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 5 tool descriptions and found no hidden instructions to the AI

Compared with others in Cybersecurityi

• More stars than 0% of the other 1004 servers in this category
• Published to the registry more recently than 75% of the other 1004 servers in this category
• Basic checks equal to or better than 33% of the other 1004 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo