Skip to main content
Glama
brendanong95

tenable-patch-management-logs-mcp

by brendanong95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tenable-patch-management-logs-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      1
      MIT

    • LogLens

      Suteerth03
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables log analysis through MCP tools for searching logs, retrieving error contexts, and summarizing incidents with self-verified root-cause hypotheses.
      6 npm
      MIT

    • Log Analyzer MCP Server

      adai78
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and analyzing logs from multiple remote Unix hosts via the Log Collector API, with tools for search, error detection, and summary generation.
      -

    • Log Analyzer MCP

      Darkstar326
      F
      license
      B
      quality
      C
      maintenance
      Enables AI-assisted analysis of log files through advanced searching, filtering, and test execution capabilities. Supports time-based queries, pattern matching, test summarization, and code coverage reporting directly within compatible MCP clients.
      12
      -

    • Tenable Security MCP

      kasireddy-sec
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-assisted vulnerability management by connecting Claude Desktop to local Nessus and Tenable Vulnerability Management, allowing natural-language queries for scan management, threat intelligence enrichment, and prioritized remediation planning.
      -
    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

    A4.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct responsibility: source lifecycle, listing, searching, timeline building, error summarization, symptom diagnosis, device comparison, and anomaly detection. Even the analysis tools are well-separated by their inputs and outputs, so an agent is unlikely to confuse them.

    Naming Consistency4/5

    The tool names mostly follow a predictable verb_noun pattern in snake_case, such as add_log_source, list_log_files, and summarize_errors. Minor deviations exist: 'explain' and 'diagnose' are bare verbs without an object, and source appears as both singular and plural, but the overall convention remains readable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a log-analysis domain. The number feels justified: source management, log discovery, search, timeline, error analysis, diagnosis, comparison, and anomaly detection all earn their place without redundancy.

    Completeness5/5

    The tool surface covers the full workflow from registering log sources, checking their health, listing and searching files, building timelines, summarizing errors, and running symptom-specific diagnoses. There are no obvious dead ends; even advanced needs like comparative and baseline anomaly analysis are addressed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources