Skip to main content
Glama
WYRE-AI

ESET PROTECT MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ESET PROTECT MCP Server

No user-submitted related servers found.

    Related Servers

    • XFA MCP

      gl-ventures
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query an organization's device posture, compliance, policies, and software/CVE status through a remote, read-only, OAuth-secured MCP endpoint.
      MIT

    • Mender MCP Server

      pasinskim
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.
      2
      MIT

    • UniFi MCP Server

      MidwestMountaineer
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage and monitor UniFi Network Controllers through natural language. Provides 25 read-only tools for discovering devices and clients, viewing security configurations, analyzing network statistics, and exporting configuration data.
      41
      MIT

    • VFS DMS ChatGPT Plugin

      mergi72
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.
      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

    B3/5.0

    Scored across 26 tools

    Disambiguation3/5

    The set follows a clear resource/action pattern, but several tools are easy to confuse: detections have v1 and v2 variants, device_os_vulnerabilities overlaps with device_vulnerabilities, and multiple patching/vulnerability-scan history tools exist. The descriptions help, but an agent must read carefully to avoid selecting the wrong list/get surface.

    Naming Consistency5/5

    Every tool is prefixed with esetprotect_ and follows a consistent snake_case verb_noun pattern, including batch_get variants. There is no mixing of conventions or unexpected naming styles.

    Tool Count3/5

    With 26 tools, the server is on the heavy side and above the ideal 3-15 range. Some consolidation is possible, especially around v1/v2 detections and multiple vulnerability/patching list tools, though the breadth is somewhat justified by the scope of ESET PROTECT.

    Completeness3/5

    The surface is almost entirely read-only: list/get/batch operations with no create, update, delete, or remediation tools. There are also no single-resource getters for device groups or vulnerability details, so some management and drill-down workflows dead-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources