Skip to main content
Glama
KhushalB25

llm-fallback-mcp

by KhushalB25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to llm-fallback-mcp

No user-submitted related servers found.

    Related Servers

    • Multi-Provider LLM MCP Server

      itachiuchihadev
      F
      license
      A
      quality
      B
      maintenance
      Unified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.
      2
      3 npm
      -

    • 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

    • multi-cloud-llm-platform

      ariz-ahmad
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes multiple LLM providers (AWS Bedrock, OpenAI, Google Gemini, local Ollama) as MCP tools with automatic routing by task type and Prometheus metrics, enabling any MCP-compatible client to generate text, route prompts, and list providers.
      -

    • litellm-mcp

      weeebdev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.
      11 npm
      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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'complete' executes the fallback completion logic, while 'health_check' verifies configuration. There is no ambiguity.

    Naming Consistency5/5

    Both tool names use a consistent verb or verb_noun pattern ('complete', 'health_check') with snake_case, making them predictable and readable.

    Tool Count5/5

    With only 2 tools, the server is tightly scoped to its core functionality: configuration check and completion execution. This count is ideal for the domain.

    Completeness5/5

    The tool surface covers all necessary operations for the fallback completion domain: confirming setup and performing the completion. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources