Patch Tuesday

Disclaimer: This is an independent, self-built project and is not an official Microsoft tool or service.

Patch Tuesday MCP Server

mcp-name: io.github.jonnybottles/patch-tuesday

Ask your AI assistant about Microsoft security updates. This Python-based MCP (Model Context Protocol) server connects AI assistants like Claude, Copilot, and ChatGPT to the MSRC Security Update Guide — the authoritative source for every CVE Microsoft patches — enabling natural-language queries over Patch Tuesday releases: CVEs, KB articles, severity ratings, CVSS scores, affected products, and exploited-in-the-wild status.

What It Does

Patch Tuesday MCP Server bridges Microsoft's official CVRF security update API and your AI assistant, allowing you to:

• Get the monthly rollup - "What did this month's Patch Tuesday fix?"
• Find what's actively exploited - "Which vulnerabilities are being exploited in the wild?"
• Look up any CVE - "Tell me about CVE-2026-41108" (KBs, affected products, CVSS, description)
• Map KBs to CVEs - "Which vulnerabilities does KB5094123 fix?"
• Filter by product - "What Critical CVEs affect Windows Server 2022 this month?"
• Track zero-days - "Were any publicly disclosed vulnerabilities patched in April?"
• See what's confirmed exploited - "Which of this month's CVEs are on the CISA KEV list?" — with federal remediation due dates
• Rank by exploitation probability - "Show me CVEs with EPSS above 50%" — daily FIRST.org exploit prediction scores
• Find zero-click, internet-reachable criticals - "Which Critical CVEs are network-reachable with no privileges and no user interaction?" — filter on the parsed CVSS attack vector, privileges, and user-interaction fields
• Jump straight to authoritative sources - every CVE detail carries ready-to-open MSRC, NVD, EPSS, and (when listed) CISA KEV reference links
• Avoid stale patches - "Is KB5087538 superseded by anything newer?" — walks Microsoft's supersedence links
• Get mitigations when there's no patch yet - "Are there mitigations or workarounds for CVE-2026-47291?" — surfaces Microsoft's mitigation, workaround, and will-not-fix guidance
• Spot trends over time - "How many HTTP.sys CVEs shipped over the last 6 months?" (months_back=6, or start_month/end_month) — aggregates matches across released months with per-month counts
• Filter by Microsoft's own exploitation forecast - "Which of this month's CVEs does Microsoft rate 'Exploitation More Likely'?" (exploitation_likely=True)
• Spot ransomware-weaponized CVEs - "Which CVEs this month are used in known ransomware campaigns?" (ransomware=True; add include_kev_details=True for the full CISA entry with required actions)
• Plan the deployment, not just the priority - "Does KB5094123 require a restart, and what build fixes it?" (include_kb_details=True adds per-KB URLs, fixed builds, supersedence, and restart requirements)
• Know what Microsoft says an update breaks - "Any known issues with KB5094126 before I roll it out?" (include_known_issues=True adds each KB's Microsoft-confirmed known issues — symptoms, workarounds, and the resolving update — best-effort from its public support page; published mainly for Windows updates, and the response says explicitly when Microsoft publishes none)
• Know what an update changes, not just what it fixes - "What's actually in KB5099536 besides the security fixes?" (include_update_summary=True adds the KB support page's summary and improvements highlights — the change-description content the MSRC security data doesn't carry — from the same page fetch as the known-issues lookup)
• Slice a month by weakness class - "Show me this month's use-after-free CVEs" (cwe="CWE-416" or cwe="use after free")
• Discover the release catalog - "Which monthly releases are available, and when were they last revised?" (list_months=True)
• Export a triage briefing - "Give me this month's Critical CVEs as a Markdown report" or "…as CSV" — a prioritized executive summary and table, or a spreadsheet-ready export (format="markdown" / format="csv")
• Force-refresh & check data freshness - "Re-pull this month's data fresh" (force_refresh=True) bypasses the in-process caches; include_freshness=True reports the cache age/TTL of the MSRC document and EPSS/KEV enrichment
• Prioritize patching - Results are sorted most-urgent-first: KEV/exploited, then EPSS, then severity, then CVSS

Perfect for security analysts, sysadmins, and IT professionals who triage Microsoft security updates every month — without clicking through the Security Update Guide portal.

Data comes from the official, public MSRC CVRF v3 API. No authentication or API key required.

Why This Server?

This is the only MCP server that models the Patch Tuesday release itself. Plenty of MCP servers can look up a CVE — general-purpose vulnerability aggregators fan a known CVE ID out across NVD, OSV, and threat-intel feeds. They answer *"tell me about CVE-X"*. But they have no concept of a monthly Microsoft release, a KB article, or a product family — so they structurally cannot answer the questions a Microsoft shop actually asks on the second Tuesday of every month:

Under the hood, the difference is the data source: this server parses the full MSRC CVRF monthly documents — the ProductTree, per-product severity threats, exploitability assessments, and KB remediation chains that per-CVE APIs never expose. That's what makes release-centric questions possible.

Other things it deliberately gets right:

• Zero API keys, zero accounts — the MSRC API is public; setup is one uvx command
• One tool, not thirty — a single consolidated msrc_search keeps your AI client's context lean and tool selection reliable
• Built for the monthly workflow — triage a release, brief your team, prioritize patching, then get on with your life

Try It Instantly — Hosted Endpoint (No Install)

A free remote instance is available at:

https://patch-tuesday-mcp.agreeabledesert-d0b8e491.eastus2.azurecontainerapps.io/mcp

No account or API key needed. The endpoint serves the same public data as a local install — for heavy use or guaranteed availability, run it locally (below) or self-host your own. Only minimal, anonymized usage data is recorded — see Telemetry & Privacy.

Requirements

General

• Python 3.11+
• An MCP-compatible client (Claude Desktop, Cursor, Claude Code, GitHub Copilot CLI, etc.)

Using uvx (Recommended)

If you are installing or running the server via `uvx`, you must have uv installed first.

• uv (includes uvx): https://github.com/astral-sh/uv

Install uv:

# macOS / Linux

curl -LsSf https://astral.sh/uv/install.sh | sh

Windows (PowerShell)

irm https://astral.sh/uv/install.ps1 | iex

uvx allows you to run the MCP server without installing the package globally.

Using pip (Alternative)

pip install patch-tuesday-mcp

Installation

Install from PyPI

uvx patch-tuesday-mcp

Or install with pip:

pip install patch-tuesday-mcp

Upgrade to Latest Version

uvx patch-tuesday-mcp@latest

Or with pip:

pip install --upgrade patch-tuesday-mcp

Quick Setup

One-click setup: Click the VS Code badge for automatic configuration (requires uv installed)

Manual setup: See instructions below for VS Code, Cursor, Claude Code, Copilot CLI, or Claude Desktop

Features

• msrc_search – Search and filter Microsoft security updates by keyword, CVE, KB number, month, product, severity, CVSS score, exploited-in-the-wild status, or public disclosure. When no month is given, results default to the most recent release whose Patch Tuesday has already occurred — the upcoming month's pre-release document (early Chromium/out-of-band entries only) is skipped by default and available explicitly via month=. Results are enriched with EPSS scores (FIRST.org 30-day exploitation probability, min_epss=0.5 filter) and CISA KEV catalog status with federal remediation due dates (kev=True filter) — both public, keyless sources. Filter by the parsed CVSS v3.x exposure fields — attack_vector (N/A/L/P), privileges_required (N/L/H), user_interaction (N/R), and scope (U/C) — to isolate, for example, network-reachable zero-click criticals; matching results surface a structured cvss object broken out from the raw vector string. Every CVE detail also includes a references block of ready-to-open links (MSRC update guide, NVD, EPSS API, and the CISA KEV catalog when the CVE is listed). Add include_chain=True to a KB lookup to walk Microsoft-stated supersedence chains (which KBs it replaces, newest → oldest). Pass a list of KB numbers (kb=["5094123", "KB5094127", ...], up to 30) to resolve them all in one call — e.g. a machine's installed-update list as context for a patch report — and get a grouped response with one per-KB entry (found or not-found, each with the same body as a single-KB lookup); every monthly document is still fetched upstream at most once for the whole batch. Add include_known_issues=True to any KB lookup (single or batched) for the Microsoft-confirmed known issues of each update — issue titles, symptoms, workarounds, and the resolving KB when Microsoft names one — scraped best-effort from the KB's public support page with an honest per-KB status: published, none_published (