Skip to main content
Glama
i-zrhe2016

xray-mcp-monitor

by i-zrhe2016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to xray-mcp-monitor

No user-submitted related servers found.

    Related Servers

    • health-monitor-mcp

      oaslananka
      A
      license
      A
      quality
      B
      maintenance
      MCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
      22
      92 npm
      2
      MIT

    • netdiag-mcp

      shigechika
      A
      license
      A
      quality
      A
      maintenance
      MCP server for on-demand network diagnostics, providing DNS lookups with DNSSEC checks, ping, traceroute, TCP port checks, HTTP checks, TLS certificate inspection, WHOIS, and ASN lookups.
      12
      MIT

    • domain-mcp

      danielgtmn
      A
      license
      A
      quality
      A
      maintenance
      MCP server for checking domain name availability via RDAP and WHOIS fallback, supporting single and bulk domain lookups.
      5
      MIT

    • Bitcoin Node MCP Server

      andy-builds-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that monitors a Bitcoin Core full node via JSON-RPC, providing tools to check node status, network info, mempool, and peer information.
      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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: creation, one-time check, listing, retrieval, manual run, enable/disable, and deletion. While run_monitor_now and check_subscription_once both perform connectivity checks, the former applies to an existing monitor while the latter is standalone, and descriptions clearly disambiguate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, with clear verbs such as register, check, list, get, run, set, and remove. The naming is uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a monitoring server, covering the full lifecycle without redundancy. Each tool serves a clear purpose and the count is neither too sparse nor overwhelming.

    Completeness4/5

    The tool set covers the full CRUD lifecycle (register, list/get, remove, set_enabled) plus a one-time check and manual run. The only notable gap is the lack of an update tool for modifying a monitor's subscription URL or schedule, but this is a minor limitation that can be worked around by removing and re-registering.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources