Skip to main content
Glama
lidless-labs

cortex-mcp

by lidless-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cortex-mcp

No user-submitted related servers found.

    Related Servers

    • CortexSynapse

      amshamah419
      F
      license
      Not graded
      quality
      D
      maintenance
      A robust MCP server that bridges AI development tools with Palo Alto Cortex platforms (XSOAR/XSIAM), enabling natural language-driven development, testing, and automation of security workflows.
      1
      -

    • MCP Splunk

      vforvishal12
      F
      license
      Not graded
      quality
      D
      maintenance
      A security-focused MCP server that enables automated log retrieval and threat analysis using LangGraph orchestration and RAG. It allows users to detect suspicious activity and generate structured security insights by integrating LLM reasoning with log data and runbook documentation.
      -

    • Cyberbro MCP Server

      stanfrbd
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that extracts Indicators of Compromise (IoCs) from unstructured text and checks their reputation across multiple threat intelligence services. It enables real-time analysis of IPs, domains, hashes, and URLs, providing enriched context for security workflows within LLMs.
      5
      19
      MIT

    • misp-mcp

      lidless-labs
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables LLMs to interact with MISP for threat intelligence sharing, IOC lookups, and event management. It provides tools for investigating indicators, discovering correlations, and exporting intelligence in formats like STIX and Suricata.
      36
      10 npm
      2
      MIT

    • pycti-mcp

      ckane
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides condensed and normalized data from OpenCTI to LLMs, enabling lookup of observables, adversaries, and reports with enriched context.
      16
      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.7/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: analyzers, responders, jobs, organizations, and users are separate domains. Within each, operations are unique (list, get, create, update, delete, enable, disable, run). Descriptions clarify any potential overlap, e.g., cortex_analyze_observable vs cortex_run_analyzer.

    Naming Consistency5/5

    All tools follow a consistent `cortex_verb_noun` pattern with snake_case. Verbs like list, get, create, run are used uniformly. Even compound verbs like `wait_and_get` fit the pattern. No mixing of styles.

    Tool Count4/5

    With 31 tools, this is a large set, but each tool corresponds to a specific operation in the Cortex security analysis platform. The count is slightly above the typical well-scoped range but justified by the platform's complexity and the need to cover analyzers, responders, jobs, organizations, and users.

    Completeness4/5

    The tool set covers core CRUD operations for analyzers, responders, jobs, organizations, and users. Notable gaps include missing delete tools for users and organizations, and no update for users besides key renewal. But the main analysis workflow is fully covered, and the gaps are minor.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources