Exploited CVEs ranked by what to patch first, with CISA KEV, EPSS and ATT&CK evidence.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Check a list of packages for known vulnerabilities via OSV.dev, then join with Patchfirst exploitation data (CISA KEV, EPSS, priority, ATT&CK techniques). Results are sorted exploited-first so you fix what attackers actually use. Ecosystems use OSV names: npm, PyPI, Maven, Go, crates.io, RubyGems, NuGet, Packagist, Debian, Alpine, etc.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http patchfirst https://patchfirst.co/mcp
Check a list of packages for known vulnerabilities via OSV.dev, then join with Patchfirst exploitation data (CISA KEV, EPSS, priority, ATT&CK techniques). Results are sorted exploited-first so you fix what attackers actually use. Ecosystems use OSV names: npm, PyPI, Maven, Go, crates.io, RubyGems, NuGet, Packagist, Debian, Alpine, etc.
| Argument | Type | Description |
|---|---|---|
| packages* | array |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"packages"
],
"properties": {
"packages": {
"type": "array",
"items": {
"type": "object",
"required": [
"ecosystem",
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Package name, e.g. \"lodash\" or \"org.apache.logging.log4j:log4j-core\""
},
"version": {
"type": "string",
"description": "Installed version. Omit to list all known vulns for the package."
},
"ecosystem": {
"type": "string",
"description": "OSV ecosystem, e.g. \"npm\", \"PyPI\", \"Maven\""
}
}
},
"maxItems": 100,
"minItems": 1
}
}
}Reverse ATT&CK lookup: which CVEs lead to a given technique, e.g. "which exploited CVEs give T1190 Exploit Public-Facing Application?". Sorted by Patchfirst priority. Parent ids include sub-techniques (T1059 matches T1059.004). Each hit shows the link's provenance badge and best evidence quote.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results, default 10, max 25. |
| kev_only | boolean | Only CVEs in CISA KEV (known exploited). Default false. |
| technique_id* | string | ATT&CK technique id, e.g. "T1190" or "T1059.004" |
| include_subtechniques | boolean | For a parent id, also match its sub-techniques. Default true. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"technique_id"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max results, default 10, max 25."
},
"kev_only": {
"type": "boolean",
"description": "Only CVEs in CISA KEV (known exploited). Default false."
},
"technique_id": {
"type": "string",
"description": "ATT&CK technique id, e.g. \"T1190\" or \"T1059.004\""
},
"include_subtechniques": {
"type": "boolean",
"description": "For a parent id, also match its sub-techniques. Default true."
}
}
}Full Patchfirst record for one CVE: description, CVSS, EPSS, CISA KEV status, the ATT&CK techniques attackers use with it (each with provenance badge, basis, evidence quotes and report links), threat reports that name it, and the priority score with its factors. Every field carries provenance and a source URL.
| Argument | Type | Description |
|---|---|---|
| cve_id* | string | CVE id, e.g. "CVE-2024-3400" |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"cve_id"
],
"properties": {
"cve_id": {
"type": "string",
"description": "CVE id, e.g. \"CVE-2024-3400\""
}
}
}Top known-exploited CVEs (CISA KEV) ranked by Patchfirst priority, optionally filtered to known ransomware use, an ATT&CK tactic (e.g. "initial-access", "Privilege Escalation", "TA0004") or a technique id. Each result lists its techniques with provenance badges.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results, default 10, max 25. |
| tactic | string | ATT&CK tactic id, name or TA id. One of: reconnaissance, resource-development, initial-access, execution, persistence, privilege-escalation, defense-evasion, stealth, defense-impairment, credential-access, discovery, lateral-movement, collection, command-and-control, exfiltration, impact |
| technique | string | ATT&CK technique id, e.g. "T1190"; parent ids include sub-techniques. |
| ransomware_only | boolean | Only KEV entries with known ransomware campaign use. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max results, default 10, max 25."
},
"tactic": {
"type": "string",
"description": "ATT&CK tactic id, name or TA id. One of: reconnaissance, resource-development, initial-access, execution, persistence, privilege-escalation, defense-evasion, stealth, defense-impairment, credential-access, discovery, lateral-movement, collection, command-and-control, exfiltration, impact"
},
"technique": {
"type": "string",
"description": "ATT&CK technique id, e.g. \"T1190\"; parent ids include sub-techniques."
},
"ransomware_only": {
"type": "boolean",
"description": "Only KEV entries with known ransomware campaign use."
}
}
}Newest CVEs by published date, with KEV/EPSS/CVSS (source data) and priority. Complete for the last 30 days (every CVE published in that window is core tier); older dates list core-tier CVEs only. Filter by a since-date and minimum CVSS severity.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results, default 20, max 100. |
| since | string | Only CVEs published on/after this date (YYYY-MM-DD). |
| min_severity | string | Minimum CVSS base severity. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Max results, default 20, max 100."
},
"since": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}",
"description": "Only CVEs published on/after this date (YYYY-MM-DD)."
},
"min_severity": {
"enum": [
"LOW",
"MEDIUM",
"HIGH",
"CRITICAL"
],
"type": "string",
"description": "Minimum CVSS base severity."
}
}
}Search every published CVE (all tiers) by CVE id (full or partial, e.g. "CVE-2024-3400", "2024-34"), vendor, product or title words (e.g. "fortinet fortios", "confluence", "sql injection"). Ranked by match quality, then priority.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results, default 10. |
| query* | string | CVE id, vendor, product or title words |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Max results, default 10."
},
"query": {
"type": "string",
"minLength": 1,
"description": "CVE id, vendor, product or title words"
}
}
}What attackers do with a CVE: its MITRE ATT&CK techniques grouped by tactic in kill-chain order (Reconnaissance -> Impact). Each technique lists every supporting link with provenance badge, basis, evidence quote and report URL, strongest provenance first.
| Argument | Type | Description |
|---|---|---|
| cve_id* | string | CVE id, e.g. "CVE-2023-4966" |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"cve_id"
],
"properties": {
"cve_id": {
"type": "string",
"description": "CVE id, e.g. \"CVE-2023-4966\""
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 20, 2026.