Skip to main content
Glama
Red Hat Security Data API MCP Server

Red Hat Security Data API MCP Server

by dmc5179

Related Servers

Alternatives to Red Hat Security Data API MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables security analysts and risk managers to query a legacy CVE registry via natural language, providing tools for searching vulnerabilities, retrieving details, and obtaining statistics.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides search, detail lookup, and gap listing tools for a security control inventory, enabling natural language queries about control status and gaps.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to query dependency security data in natural language, including trust scores for individual packages, full project scans, blast radius analysis, zombie and typosquat detection, package comparisons, and safer migration suggestions. Results can be returned inline or written as JSON reports.
      79 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language queries across AWS multi-account security scan history, including infrastructure configurations, public exposures, and organizational relationships.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for OSIDB (Red Hat Product Security's vulnerability management system). Enables read-only querying of flaws, affects, trackers, and status via natural language from MCP clients like Cursor or Claude Desktop.
      83 PyPI
      2
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource type and action: CSAF search/detail, CVE search/detail, and OVAL list/retrieve. The resource nouns are explicit, so there is no meaningful overlap between search_csaf and search_cves or between the detail retrieval tools.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern with search_, get_, and list_ prefixes. The naming is consistent and predictable: search_* for queries, get_*_details/get_*_stream for fetching individual items, and list_* for enumerating available streams.

    Tool Count5/5

    Six tools is well-scoped for a security data lookup server. The set covers three data types with paired search/list and detail retrieval operations, and every tool maps to a meaningful API action without redundancy or bloat.

    Completeness5/5

    The server provides both discovery/search and full-detail access for CSAF advisories, CVEs, and OVAL streams. As a read-only security data API, no create/update/delete operations are expected, and the retrieval lifecycle is effectively complete.