Skip to main content
Glama
Sign In
patch-tuesday-mcp

patch-tuesday-mcp

by jonnybottles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to patch-tuesday-mcp

No user-submitted related servers found.

    Related Servers

    • cvescout

      zember
      A
      license
      A
      quality
      B
      maintenance
      Enables any MCP client (Claude Code, Claude Desktop, Codex, or a custom agent) to fetch the latest CVEs at query time from live sources — NVD, CVE List V5, GitHub Advisory Database, CISA KEV and FIRST EPSS — without a separate API key. Exposes search, filtering (severity, RCE, PoC, KEV, keyword, CPE), per-CVE detail and risk-scored patch prioritization as JSON tools, so answers are grounded in live data rather than model memory.
      6
      1
      MIT

    • CVE Risk MCP Server

      sarveshkapre
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables CVE lookups and risk assessment by integrating CISA Known Exploited Vulnerabilities (KEV) data and CVSS metrics. It helps users prioritize patching efforts by ranking vulnerabilities based on exploitation status and calculated risk scores.
      MIT

    • CVE Intelligence MCP

      munyong-mmy
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables querying official CVE List V5 records enriched with CISA KEV data, including single or batch CVE lookups and required-action guidance for known exploited vulnerabilities.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no risk of confusion between tools. The tool's purpose is clearly defined.

    Naming Consistency5/5

    With a single tool, naming consistency is not an issue. The name 'msrc_search' is descriptive and follows a clear convention.

    Tool Count3/5

    Having only one tool for the entire server is borderline. While the tool is comprehensive, bundling all functionality (search, CVE/KB lookup, trends) into one makes it complex and less discoverable. A small set of separate tools would be more appropriate.

    Completeness5/5

    The single tool covers all expected operations for the MSRC domain: searching, filtering, CVE/KB detail, historical trends, pagination, stats, and enrichment. There are no apparent gaps in the tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Resources