Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool owns a distinct capability: point lookup by ID (get_record), free-text/faceted search (search_vulnerabilities), a curated recency feed (list_recent_exploited), and two vocabulary/coverage helpers (list_sources, list_technologies). The descriptions explicitly resolve the two plausible overlaps — get_record vs search_vulnerabilities for known IDs, and list_recent_exploited vs search_vulnerabilities with known_exploited_only — with inline 'use X instead' guidance.

Naming Consistency5/5

All five names follow a strict snake_case verb_noun pattern (get_record, list_recent_exploited, list_sources, list_technologies, search_vulnerabilities). Verbs are used precisely: get for single-record fetch, list for enumerations, search for query. No mixed conventions.

Tool Count5/5

Five tools is well within the ideal range and each earns its place: two retrieval primitives, one discovery feed, and two introspection helpers that directly prevent failed searches. There is no filler or near-duplicate tool to trim.

Completeness4/5

As a read-only vulnerability-intel corpus, the surface covers the core lifecycle: resolve by any ID, search by words/technology/kind/exploitation, and discover valid filter labels and source coverage, plus pagination on both listing tools. Minor gaps remain — no explicit date-range or CISA-deadline filter surfaced, and no way to enumerate records per source or export a technology's full record set — but agents can work around these via search.

Available Tools

5 tools
get_recordGet one record with full evidenceA
Read-only
Inspect

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.

Inputs: id (required).

list_recent_exploitedRecently exploited vulnerabilitiesA
Read-only
Inspect

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.

Inputs: days, limit, offset.

list_sourcesList data sources and their statusA
Read-only
Inspect

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.

Inputs: no named parameters.

list_technologiesList technology labelsA
Read-only
Inspect

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.

Inputs: limit, query.

search_vulnerabilitiesSearch vulnerabilities, breaches, and advisoriesA
Read-only
Inspect

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.

Inputs: kind, sort, limit, query, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides cached, structured snapshots of recent CVEs and GitHub Security Advisories, enabling AI agents to lookup CVEs, find vulnerabilities for a package by ecosystem, list recent critical CVEs, and get severity summaries.
      4
      2,119 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search, correlate, and monitor real-time vulnerability intelligence from NVD, CISA KEV, EPSS, and MITRE ATT&CK, including CVE details, critical CVE tracking, known exploited vulnerabilities, and exploitation probability scores.
      5
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to a live, sourced feed of publicly reported breaches, ransomware claims, exploited CVEs, malicious packages and connectivity drops, each tagged with an honest status. Enables agents to check whether a user's software stack is affected and retrieve plain-text fix runbooks for one-click remediation.
      154
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources