Koskamo

KEVWire MCP

An official MCP server providing read-only access to KEVWire's security intelligence corpus, including CISA KEV, critical CVEs, breaches, and AI security incidents. It allows AI agents to search vulnerabilities, retrieve specific records with primary sources, list recent exploited items, and explore technologies and sources without authentication.

Visit Blake Elliot, Inc.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

KEVWire MCP logo, by Blake Elliot, Inc.Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Blake Elliot, Inc.
MCP endpoint (Streamable HTTP)
https://kevwire.com/mcp
Vendor documentation

What you can do with it

  • Search for specific vulnerabilities or CVEs
  • Retrieve detailed records with primary source links
  • List recently exploited vulnerabilities
  • Explore available technologies and data sources

Source and maintenance

Vendor evidenceRegistry 6.0.0
mcp-registry: com.kevwire/kevwire@6.0.0Project website

Protocol and capabilities

Server
kevwire 6.0.0
MCP protocol
2025-06-18
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Read-only security intelligence. Cite the source URLs in each record, not KEVWire alone, for factual claims. Known exploitation and CISA KEV membership are different facts; federal due dates are not an organization's SLA. Missing metrics mean unknown, not zero.

Tools

5 advertised

search_vulnerabilities — Search vulnerabilities, breaches, and advisories
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

search_vulnerabilities input schema
{
  "type": "object",
  "properties": {
    "kind": {
      "enum": [
        "vulnerability",
        "breach",
        "advisory",
        "ai-research"
      ],
      "type": "string"
    },
    "sort": {
      "enum": [
        "urgent",
        "newest",
        "priority",
        "cvss",
        "epss"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 500,
      "description": "Words to match, e.g. \"php rce\", a CVE ID, a product, or an event name like \"PHP2Shell\"."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 100000,
      "minimum": 0
    },
    "technologies": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 120
      },
      "maxItems": 50,
      "description": "Technology labels, e.g. [\"Microsoft Windows\", \"PHP\"]. Matches any."
    },
    "known_exploited_only": {
      "type": "boolean",
      "description": "Only records in the CISA Known Exploited Vulnerabilities catalog."
    }
  },
  "additionalProperties": false
}
search_vulnerabilities annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_record — Get one record with full evidence
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

get_record input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 200
    }
  },
  "additionalProperties": false
}
get_record annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
list_recent_exploited — Recently exploited vulnerabilities
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_recent_exploited input schema
{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "default": 30,
      "maximum": 365,
      "minimum": 1
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 100000,
      "minimum": 0
    }
  },
  "additionalProperties": false
}
list_recent_exploited annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
list_technologies — List technology labels
Advertised by the server during the last successful anonymous check.
Advertised read-only

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_technologies input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 500,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 120
    }
  },
  "additionalProperties": false
}
list_technologies annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
list_sources — List data sources and their status
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

list_sources input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
list_sources annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
190 ms
95th percentile latency
190 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 190 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http kevwire-mcp https://kevwire.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add kevwire-mcp --url https://kevwire.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable kevwire-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "kevwire-mcp": {
      "url": "https://kevwire.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "kevwire-mcp": {
      "type": "streamableHttp",
      "url": "https://kevwire.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start kevwire-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "kevwire-mcp": {
      "type": "http",
      "url": "https://kevwire.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http kevwire-mcp https://kevwire.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "kevwire-mcp": {
      "url": "https://kevwire.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "kevwire-mcp": {
      "serverUrl": "https://kevwire.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like KEVWire MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,362

Do you run KEVWire MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing