Skip to main content
Glama
Space-C0wboy

ReliaQuest GreyMatter MCP Server

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ReliaQuest GreyMatter MCP Server

No user-submitted related servers found.

    Related Servers

    • watchTowr Platform MCP Server

      watchtowr
      F
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to the watchTowr Platform for real-time access to external attack surface data, findings, and threat intelligence. Provides 113 tools for querying and managing assets, findings, hunts, and more.
      -

    • Grafana MCP Server

      0xteamhq
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with Grafana dashboards, datasources, alerts, incidents, and monitoring data through 43 comprehensive tools. Supports querying Prometheus metrics, Loki logs, managing incidents, and dashboard operations with full authentication support.
      43
      391 npm
      3
      MIT

    • xsiam-mcp

      CoveoSec
      A
      license
      B
      quality
      C
      maintenance
      Exposes the entire Palo Alto Cortex XSIAM REST API (129 operations across 26 categories) as MCP tools, plus composite tools like xql_query for AI agents to search and investigate security data.
      100
      Apache 2.0

    • rapid7-mcp

      solomonneas
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to interact with Rapid7 InsightIDR SIEM for investigating incidents, searching logs with LEQL, managing alerts and assets, analyzing user behavior, and handling threat intelligence.
      26
      6 npm
      4
      MIT
    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

    C2.1/5.0

    Scored across 147 tools

    Disambiguation2/5

    With 147 tools, many have overlapping purposes. Singular/plural pairs like `drp_alert`/`drp_alerts` and `watch_drp_alert`/`watch_drp_alerts` create confusion, as do similar actions like `close_case` and `cancel_case`. An agent will struggle to select the correct tool without deep inspection.

    Naming Consistency3/5

    Most tools follow a snake_case verb_noun pattern (e.g., `create_case`, `update_user`), but there are inconsistencies such as `un_watch` (with underscore), `upsert` variants, and bare-noun queries like `incidents` and `me`. The long compound verb `acknowledge_assign_and_close_incident` also deviates.

    Tool Count1/5

    147 tools is an extreme number for any MCP server, far exceeding typical scoping. This overwhelms agents and makes selection error-prone.

    Completeness5/5

    The tool set covers a wide range of GreyMatter capabilities across incidents, cases, tasks, DRP alerts, playbooks, reference lists, and user management, with CRUD and lifecycle operations. The inclusion of a generic `graphql_query` tool fills any remaining gaps, making coverage effectively complete.

    Maintenance

    ActivityNo data
    ResponsivenessResponsive

    Resources