Skip to main content
Glama
ukkugh

tenable-identity-exposure-mcp

by ukkugh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tenable-identity-exposure-mcp

No user-submitted related servers found.

    Related Servers

    • Tenable Identity Exposure MCP

      knethteo
      A
      license
      A
      quality
      D
      maintenance
      Exposes the Tenable Identity Exposure (TIE) REST API as tools for LLM clients, enabling queries on security profiles, activity timelines, AD objects, and more.
      15
      5
      MIT

    • tie-mcp-server

      taherkaraki
      A
      license
      C
      quality
      C
      maintenance
      MCP server for the Tenable Identity Exposure API, providing 131 tools for complete API coverage with multi-tenant support and granular security controls.
      100
      11 npm
      17
      MIT

    • tenable-vpr-mcp

      Sabastiaz
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Tenable.io/One Vulnerability Management that provides read-only tools for querying scans, assets, plugins, and vulnerabilities, plus specialized reporting tools for VPR re-prioritization, CISA KEV/EPSS exposure, and scan delta comparisons.
      11
      3
      MIT

    • ransomware-live-mcp

      abdulbrown
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to query the ransomware.live PRO threat-intelligence API through 25 read-only tools covering ransomware group TTPs, victims, IOCs, YARA rules, ransom notes, leaked negotiation chats, press coverage, SEC 8-K disclosures, and CSIRT contacts.
      25
      MIT

    • tenable-activity-mcp

      brendanong95
      A
      license
      A
      quality
      B
      maintenance
      Enables querying and analyzing Tenable Vulnerability Management audit logs, including activity summaries, API key usage, and anomaly detection through MCP tools.
      6
      MIT

    • Darktrace MCP

      nuoframework
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables investigation of devices, model breaches and analyst incidents from an MCP host through a bounded set of read-only tools, with operator-controlled profiles and a fixed operation inventory. Writes, PCAP export, email and HTTP transport are excluded, and responses are minimized and escaped before entering model context.
      0
      1
      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

    A3.9/5.0

    Scored across 17 tools

    Disambiguation3/5

    Several tools overlap in purpose: tie_deviances, tie_deviances_by_checker, tie_deviances_by_directory, and tie_deviances_bulk all query deviances with different parameterizations. tie_resource_action and tie_request both provide generic API access, and tie_recent_activity overlaps with tie_alerts and tie_attacks. Descriptions mitigate some ambiguity, but agents may struggle to pick the right tool for time-bounded deviance queries.

    Naming Consistency3/5

    All tools share the 'tie_' prefix, but naming patterns are inconsistent: some are verb_noun (tie_search_events), some are noun_phrase (tie_checkers_summary, tie_deviances_bulk), and a few are single nouns (tie_profiles, tie_catalog). The lack of a uniform verb_noun or action-first convention makes the set feel less predictable.

    Tool Count3/5

    With 17 tools, the set sits just above the ideal 3-15 range. The sheer number of deviance query variants (four) and generic utilities (catalog, request, resource_action) inflate the count, though the complexity of the TIE API partially justifies the breadth.

    Completeness4/5

    The tool surface covers most core workflows: discovery, topology, scores, events, deviances, attacks, and alerts. Generic CRUD via tie_resource_action fills in gaps. However, there is no explicit tool for mutating deviance state (e.g., ignore or resolve), and the generic tools may not expose all such endpoints cleanly, representing a notable gap.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources