Skip to main content
Glama
knethteo

Tenable Identity Exposure MCP Server

by knethteo

Related Servers

Alternatives to Tenable Identity Exposure MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides MCP tools to query the Tenable Identity Exposure (TIE) API for security profiles, deviances, attacks, and activity timelines, with enforced read-only mode to protect credentials.
      17
      MIT
    • 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
    • A
      license
      B
      quality
      C
      maintenance
      Connects AI clients to Tenable OT Security, exposing OT/ICS asset inventory, vulnerabilities, events, policies, and findings as read tools, with an opt-in dry-run write layer for asset edits and policy management.
      59
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.
      36
      9 npm
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Exposes the 1E Platform Consumer API as 92 callable MCP tools, enabling MCP-compatible LLM clients to manage devices, instructions, approvals, users, groups, custom properties, and other resources across a 1E DEX tenant.
      92
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Exposes the Timely.mn v3 time-attendance API as MCP tools for Claude and other clients, allowing queries for company-wide attendance, employee profiles, and attendance reports.
      4
      -

    TDQS

    A4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is slight overlap among tie_deviances, tie_deviances_by_checker, and tie_deviances_by_directory. However, descriptions clarify that they differ by date filtering and scoping, so ambiguity is minimal.

    Naming Consistency5/5

    All tools use the consistent 'tie_' prefix and follow snake_case naming. Naming patterns are predictable: nouns for entity listings (tie_alerts, tie_attacks) and verb_noun for search actions (tie_search_ad_objects). No mixed conventions.

    Tool Count5/5

    15 tools is well-scoped for the Tenable Identity Exposure domain. Each tool covers a distinct aspect (alerts, attacks, deviances, profiles, search, topology) without unnecessary duplication or missing core functionality.

    Completeness5/5

    The tool set comprehensively covers the API surface: CRUD via tie_resource_action, specific queries for alerts, attacks, deviances, scores, topology, and search. The tie_recent_activity tool fills a gap by merging IoE and IoA timelines. No obvious missing operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues