# Patchfirst MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.patchfirst%2Fpatchfirst
Registry id: `mcp-registry/co.patchfirst/patchfirst`
Status: live (checked 2026-11-22T17:30:45.100Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 307
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "patchfirst-mcp-server": {
      "type": "http",
      "url": "https://patchfirst.co/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http patchfirst-mcp-server https://patchfirst.co/mcp
```

## Tools (7)

- `check_stack`: Check a list of packages for known vulnerabilities via OSV.dev, then join with Patchfirst exploitation data (CISA KEV, EPSS, priority, ATT&CK techniques). Resul
- `cves_for_technique`: 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 pri
- `get_vulnerability`: 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, ev
- `list_exploited`: Top known-exploited CVEs (CISA KEV) ranked by Patchfirst priority, optionally filtered to known ransomware use, an ATT&CK tactic (e.g. "initial-access", "Privil
- `list_feed`: 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); o
- `search`: 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", "c
- `techniques_for_cve`: What attackers do with a CVE: its MITRE ATT&CK techniques grouped by tactic in kill-chain order (Reconnaissance -> Impact). Each technique lists every supportin

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
