Skip to main content
Glama
Sign In
acronis-mcp

acronis-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to acronis-mcp

No user-submitted related servers found.

    Related Servers

    • abnormal-mcp

      GregDog
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to query Abnormal Security for threats, message search, remediation history, ATO cases, vendor/BEC data, and opt-in evidence download and response actions.
      Apache 2.0

    • RocketCyber MCP Server

      MSPbotsAIFramework
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read a managed SOC's customer data, including confirmed incidents, detection app events and summaries, agent and firewall inventory, detection apps, account hierarchy, and Microsoft Defender and Microsoft 365 status. All operations are read-only, stateless, and multi-tenant via a per-request API key header.
      Apache 2.0

    • CyberQP MCP Server

      WYRE-AI
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.
      10
      Apache 2.0

    • Aegis

      nithyajangam
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables governing tenant-aware MCP tools with policy enforcement, scoped access, human approval workflows, and tamper-evident audit logging.
      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

    C2.8/5.0

    Scored across 34 tools

    Disambiguation3/5

    The tenant, user, policy, resource, agent, and incident tools are mostly distinguishable. However, the alert surface has many overlapping-sounding tools such as fetch_all_alerts, fetch_alert_counters, fetch_alerts_grouped_by_scope, fetch_alerts_grouped_per_customer, fetch_alert_counts_per_customer, and fetch_active_alert_count, so selecting the right one requires careful reading.

    Naming Consistency4/5

    Nearly all tools use a consistent acronis_ prefix followed by snake_case fetch_* names, with one search_ exception. Minor variations like fetch_alert vs fetch_all_alerts and grouped/count naming are readable and predictable.

    Tool Count2/5

    At 34 tools, the surface is large for a single MCP server and is especially heavy in alert-related read variants. Several alert count/grouping tools could likely be consolidated without losing capability.

    Completeness3/5

    The server provides broad read-only coverage across tenants, users, alerts, policies, resources, agents, and incidents. However, it lacks lifecycle or mutation operations such as creating/updating policies, acknowledging or resolving alerts, or starting response actions, and fetch_response_action_status has no corresponding action-start tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources