Skip to main content
Glama
lyonzin

Cymulate MCP Tools

by lyonzin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Cymulate MCP Tools

No user-submitted related servers found.

    Related Servers

    • fieldeffect-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Field Effect MDR (Covalence) that exposes organization, endpoint device, and active response reporting endpoints as tools, enabling security management via natural language.
      -

    • eSentire Atlas MCP Server

      omichelbraga
      F
      license
      A
      quality
      B
      maintenance
      Exposes eSentire Atlas API (Findings, Ticketing, MVS) and Threat Intelligence feeds (IP Watch, Advanced/STIX) as MCP tools, enabling security operations and threat intelligence queries through natural language.
      29
      -

    • CyberSecurityLab MCP Server

      dbolatti
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides an educational MCP server with cybersecurity examples, exposing a threat-intel lookup tool, an asset inventory resource, and an investigation prompt using simulated data.
      -

    • connectsecure-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for ConnectSecure vulnerability management, exposing 285 read-only tools to query assets, vulnerabilities, Active Directory, and more via natural language.
      -

    • usap-skills

      jaskaranhundal
      A
      license
      A
      quality
      A
      maintenance
      Exposes 79 cybersecurity skills and 12 orchestrator agents over MCP, with a typed 11-field output contract, an enforced resolvable-evidence gate (no verdict without a resolvable source), and human-approval gating for every mutating action. Apache-2.0, stdlib-only.
      8
      4
      Apache 2.0
    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.9/5.0

    Scored across 120 tools

    Disambiguation3/5

    With 120 tools, there are many overlapping list/get operations for different modules (e.g., env_list vs env_list_v1, multiple get_filters, multiple get_history_ids). However, descriptions are specific enough to differentiate most tools, and the fallback cymulate_api_call is explicitly a catch-all. Some ambiguity remains, but it is mitigated by clear documentation.

    Naming Consistency4/5

    Most tools follow a consistent cymulate_<module>_<resource>_<action> pattern, but there are notable exceptions like cymulate_health, cymulate_debug_last_request, cymulate_ttp_designer, and cymulate_killchain_designer. Versioned names (cymulate_env_list_v1) and compound actions (cymulate_ev_launched_get_configurations) also deviate slightly. Overall, the conventions are predictable but not perfectly uniform.

    Tool Count1/5

    120 tools is far beyond the reasonable scope for an MCP server, even for a comprehensive API wrapper. This overwhelms agents and makes selection harder. The calibration explicitly marks 50+ tools as an extreme mismatch.

    Completeness5/5

    The server covers nearly every domain of the Cymulate platform—EV, EA, BAS, Advanced, ASM, Immediate Threats, FKC, environments, agents, remediation, and platform analytics. CRUD operations exist for major resources, and the fallback cymulate_api_call ensures no endpoint is unreachable. The tool surface is thorough and has no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources