Skip to main content
Glama
Sign In
mihomo-ai-failover

mihomo-ai-failover

by doublebearoliver-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mihomo-ai-failover

No user-submitted related servers found.

    Related Servers

    • mihomo-mcp

      wlor0623
      A
      license
      A
      quality
      C
      maintenance
      Enables AI/MCP clients to manage a local mihomo/Clash Meta core by switching proxies, testing latency, viewing or closing connections, changing modes, and toggling TUN and Windows system proxy settings through a named pipe or HTTP control channel.
      10
      MIT

    • remote-mcp-hub-mac

      etern1ty-crypto
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables macOS users to securely connect AI assistants such as Notion AI, Claude, and Cursor to their local files and terminal through an MCP server protected by a Bearer token and Cloudflare Tunnel.
      MIT

    • Multi-LLM Gateway MCP

      tgosoul2019
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that functions as an intelligent gateway for multiple LLM backends including OpenAI, Claude, and Ollama. It supports automatic provider fallback, streaming responses via Server-Sent Events, and real-time monitoring for robust AI integration.
      MIT

    • Kilobat

      seifip
      A
      license
      Not graded
      quality
      B
      maintenance
      A stdio MCP server exposing 43 tools that let AI agents diagnose and monitor a Mac's networking: which apps use bandwidth, Wi-Fi signal and channels, latency and packet loss, DNS and speed tests, why a host or API won't connect, whether traffic leaves via VPN, hotspot data budgets, and keeping the machine awake during long jobs. Read-only tools run without confirmation, while tools that change system settings prompt the agent to ask the user first.
      1
      GPL 3.0
    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

    A3.8/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes, but a few pairs like get_status/list_pools and check_provider_paths/run_health_check could be confused without careful reading. The detailed descriptions help differentiate them, so overall ambiguity is low.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., preview_install, run_health_check, uninstall_monitor). There are no mixed conventions, and the verb clearly indicates the action.

    Tool Count4/5

    With 20 tools, the set is on the heavier side, but each tool addresses a distinct phase of the failover lifecycle (preview, install, monitor, rollback). Given the complexity of the domain, the count is justifiable, though some status tools could potentially be consolidated.

    Completeness4/5

    The tool surface covers the full lifecycle from environment diagnosis and provider overrides to installation, monitoring, and uninstallation. Minor gaps exist, such as no direct tool for updating failover settings after initial config, but users can work around this.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources