Skip to content

Patchfirst MCP server

co.patchfirst/patchfirstpatchfirst.costreamable-httpv1.0.0Scanned

Exploited CVEs ranked by what to patch first, with CISA KEV, EPSS and ATT&CK evidence.

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Patchfirst MCP server can do

The Patchfirst MCP server is published by patchfirst.co, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: techniques_for_cve, cves_for_technique and check_stack), but cannot delete data. 4 tools only read.

1 tool brings in text other people can write (check_stack).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • check_stackCheck a list of packages for known vulnerabilities via OSV.dev, then join with Patchfirst exploitation data (CISA KEV, EPSS, priority, ATT&CK techniques).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • cves_for_techniqueReverse ATT&CK lookup: which CVEs lead to a given technique, e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • techniques_for_cveWhat attackers do with a CVE: its MITRE ATT&CK techniques grouped by tactic in kill-chain order (Reconnaissance -> Impact).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • get_vulnerabilityFull 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 re…No findings

    Why it is in this group

    • The name "get_vulnerability" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_exploitedTop known-exploited CVEs (CISA KEV) ranked by Patchfirst priority, optionally filtered to known ransomware use, an ATT&CK tactic (e.g.1 finding

    Why it is in this group

    • The name "list_exploited" says "list": a word for reading.

    Findings

    • Info

      The input schema at properties.tactic.description mentions "credential".

      Matched text

      inputSchema.properties.tactic.description: "...e-evasion, stealth, defense-impairment, credential-access, discovery, lateral-movement, co..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_feedNewest CVEs by published date, with KEV/EPSS/CVSS (source data) and priority.No findings

    Why it is in this group

    • The name "list_feed" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:18 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://patchfirst.co/mcp: tools/list returned 7 tools to an anonymous client, including techniques_for_cve (write), cves_for_technique (write), check_stack (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The input schema at properties.tactic.description mentions "credential".

    Matched text

    inputSchema.properties.tactic.description: "...e-evasion, stealth, defense-impairment, credential-access, discovery, lateral-movement, co..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__patchfirst__get_vulnerability",
      "mcp__patchfirst__list_exploited",
      "mcp__patchfirst__list_feed",
      "mcp__patchfirst__search"
    ],
    "ask": [
      "mcp__patchfirst__techniques_for_cve",
      "mcp__patchfirst__cves_for_technique",
      "mcp__patchfirst__check_stack"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as patchfirst. Review it before you use it.

Capability tags behind 1 rule
  • mcp__patchfirst__check_stack untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.patchfirst/patchfirst/verify?hash=bb5e1b0d678153e4f52069ee9700e17858a09626e4b57c4e53ae6e9ed4a5bae7" | jq -e '.changed == false'

Pinned hash bb5e1b0d6781, from Nov 20, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.patchfirst/patchfirst/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.patchfirst/patchfirst
[![Anlyon Radar](https://radar.anlyon.com/badge/co.patchfirst/patchfirst.svg)](https://radar.anlyon.com/servers/co.patchfirst/patchfirst)

Source: MCP Registry. Synced Nov 20, 2026, 06:17 UTC.

Patchfirst MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Patchfirst MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Patchfirst MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Patchfirst MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Patchfirst MCP server have?

7 tools: 3 write, 4 read. techniques_for_cve, cves_for_technique, check_stack, get_vulnerability, list_exploited, list_feed and search.

Does the Patchfirst MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Patchfirst MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Patchfirst MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.