Skip to main content
Glama
omichelbraga

eSentire Atlas MCP Server

by omichelbraga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to eSentire Atlas MCP Server

No user-submitted related servers found.

    Related Servers

    • cti-mcp-server

      TopCaver
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides threat intelligence tools like IoC lookups, event backtracking, and IP enrichment via MCP, enabling automated triage and evidence queries.
      1
      -
    • Purple AI MCP Server by Sentinel-One

      Purple AI MCP Serverofficial

      Sentinel-One
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to interact with SentinelOne's cybersecurity platform for security analysis, threat investigation, and asset management through natural language queries. Provides read-only access to alerts, vulnerabilities, misconfigurations, and inventory data.
      33
      98
      MIT

    • QRadar MCP Server

      caohonghoa98
      F
      license
      Not graded
      quality
      C
      maintenance
      Bridges LLMs to IBM QRadar SIEM via 4 intelligent MCP tools covering 728 REST API endpoints, enabling natural language queries for offenses, assets, rules, and more.
      -

    • 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.
      -

    • tenable-mcp

      nguyenthdat
      A
      license
      A
      quality
      C
      maintenance
      Exposes Tenable security operations as MCP tools for AI-powered security workflows, enabling asset, vulnerability, scan, plugin, and tag management via natural language.
      17
      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

    A3.5/5.0

    Scored across 29 tools

    Disambiguation4/5

    The major domains are cleanly separated by tickets_, ti_, findings/finding_, and mvs_ prefixes, and most tools target a distinct resource+action. The only mild ambiguity comes from near-variant tools such as findings_search vs findings_search_advanced and ti_indicators vs ti_indicators_paged vs ti_indicators_misp, but their descriptions explain the differences.

    Naming Consistency4/5

    Most names follow a verb_noun pattern under a clear domain prefix, e.g. tickets_list_cases, mvs_get_asset, and ti_check_ip. A few deviations such as tickets_case_type_configs, mvs_asset_details, mvs_assets_affected_by, and finding_update alongside findings_search prevent a perfect score, but the style is otherwise consistent and readable.

    Tool Count3/5

    29 tools feels heavy for an MCP surface and will consume meaningful agent context, placing the server above the ideal 3-15 range. The count is partly justified by the broad eSentire platform scope spanning cases, threat intel, findings, and MVS, but it is still borderline and could reasonably be split into separate servers.

    Completeness4/5

    The surface covers the core case lifecycle, findings search/update, threat-intel feeds, and MVS asset/vulnerability/patch workflows well. Minor gaps include no direct single-finding fetch and no support for attachments over 5MB, but agents can usually work around these using the existing search and metadata tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources