Skip to main content
Glama
GeiserX

duplicacy-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to duplicacy-mcp

No user-submitted related servers found.

    Related Servers

    • duplicacy-mcp

      SeraphimSerapis
      A
      license
      A
      quality
      C
      maintenance
      MCP server for administering Duplicacy backups via the duplicacy-web API, enabling AI clients to inspect and manage storages, repositories, schedules, and jobs.
      15
      MIT

    • Proms MCP Server

      app-sre
      A
      license
      Not graded
      quality
      D
      maintenance
      A lean MCP server that provides LLM agents with transparent access to multiple Prometheus instances for metrics analysis and SRE operations.
      4
      GPL 2.0
    • prometheus-mcp-server by prometheus

      prometheus-mcp-serverofficial

      prometheus
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that lets LLMs interact with a running Prometheus instance via its API, enabling metric analysis, PromQL queries, and rule/target inspection. It also provides embedded documentation and guided runbooks for common Prometheus tasks.
      132
      Apache 2.0

    • Prometheus MCP Server

      CaesarYangs
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables Large Language Models to retrieve, analyze, and query metric data from Prometheus databases through pre-defined routes.
      33
      MIT

    • Prometheus MCP Server

      bartest5
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to query and analyze Prometheus metrics through PromQL, with support for metric discovery and authentication.
      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

    A4.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools mostly have clearly distinct monitoring purposes: overview is an aggregate health check, status is one snapshot, and history is the last completed run. The main ambiguity is between get_backup_status and get_backup_history, since both return last-run details, but the descriptions explicitly distinguish current state versus completed-run history.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get_backup_history, get_backup_overview, get_backup_status, get_prune_status, get_storage_usage, and list_snapshots. The use of list_snapshots instead of get_snapshots is still a conventional verb_noun choice and does not break readability.

    Tool Count5/5

    Six tools is well-scoped for a read-only Duplicacy backup monitoring server. Each tool maps to a distinct monitoring concern: discovery, per-snapshot status/history, aggregate health, prune status, and storage usage.

    Completeness4/5

    The surface covers the core monitoring workflows: discovering snapshots, checking backup health, inspecting a snapshot, reviewing last-run history, prune status, and storage usage. Minor gaps exist, such as no explicit standalone tool for listing storage targets or machines, but list_snapshots exposes those values and agents can work around this.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources