ESET PROTECT MCP Server
Related Servers
Alternatives to ESET PROTECT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read protected computers and their check-ins, computer groups, approval requests, the unified audit log, and child organizations through a zero-trust endpoint security portal API. Every operation is read-only, with credentials supplied per request as headers and never stored.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI assistants to search agents, triage alerts, review target groups, organizations, and locations, follow scans and tasks, inspect rules and extensions, and—with explicit confirmation—scan or isolate hosts through the Datto EDR API.36Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query vulnerability management, security center, identity exposure, and cloud security data read-only, and to export Active Directory data from identity exposure into a BloodHound attack graph.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceEnables 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.2MIT
- AlicenseAqualityFmaintenanceEnables an AI assistant to perform read-only defensive security lookups and analysis, including privacy-preserving breach checks, CVE and MITRE ATT&CK queries, log parsing, IOC defanging/refanging, hashing, and Windows event ID explanations.9MIT
TDQS
Scored across 26 tools
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.
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.
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.
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.