relayer-mcp
Related Servers
Alternatives to relayer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables automated VPS initialization and management through SSH connections. Supports installing common services like Node.js, Nginx, and Redis, configuring domains with SSL certificates, and setting up GitHub CI/CD pipelines with deploy keys.53MIT
- AlicenseBqualityBmaintenanceEnables users to inspect and manage domains, DNS records (including A, AAAA, CNAME, MX, TXT and more), HTTP forwards, invoices and dynamic DNS through a hosting provider's API, with previewed change plans, conflict detection, backups and independent readback before writes. Offers DNS shortcuts such as website setup, verification records, bulk IP replacement, zone import/export and backup restore, exposed via local stdio or authenticated Streamable HTTP for a central gateway.27MIT
- AlicenseAqualityCmaintenanceAgent-safe management of independent Solana validators and RPC nodes over MCP and CLI: Solana-aware status, in-place upgrades, and DNS failover. Every change is dry-run by default, policy-gated, and audited, and it never touches keypairs.15Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides an agent toolbelt exposing 74 tools spanning files, shell, web, code graph, git, memory, computer, and axodex behind a single process, plus optional gateway endpoints for model routing, verification, and context packing. Ships dual-era MCP support over stdio or Streamable HTTP, with hardcoded tool groups importable for the axo ecosystem.45 npmMIT
- AlicenseAqualityCmaintenanceProduction-ready, zero-knowledge AI DevOps deployment, infrastructure provisioning, self-healing execution, and persistent documentation engine for VPS servers.204MIT

heliographofficial
AlicenseAqualityBmaintenanceRuns commands on machines you cannot SSH into by publishing steps to a transport the far side already reaches (git, file share, S3, relay), then reads back a log with every line timestamped in UTC. Seven tools cover send, status, logs, stall detection and a pre-flight check.7Apache 2.0
TDQS
Scored across 15 tools
Each tool targets a distinct phase or action in the relayer lifecycle: prerequisites, account, install, health, claim, VPD, storage, CLI, settings, restart, backups. There is no overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., check_prerequisites, start_claim, update_settings). The verbs clearly indicate the action and the noun indicates the target, making the naming predictable and readable.
With 15 tools, the set covers the full installation and management workflow without being bloated. Each tool serves a specific, necessary function in the operator's journey, and the count is within the well-scoped range for a server with this purpose.
The tool set covers the entire lifecycle from prerequisites to installation, claiming, configuration, verification, settings tuning, restart, and backups. There are no obvious dead ends or missing operations for the intended use case of installing and managing an XNS Relayer.