Skip to main content
Glama
UplinkSwitch MCP server

UplinkSwitch MCP server

Official
by uplinkswitch

Related Servers

Alternatives to UplinkSwitch MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to browse a live catalog of 100+ models with pricing, rankings and measured uptime, check credits and spend, and send chat completions through an OAuth-authenticated, per-connection key capped by a spend limit. Read tools are free, and paid calls are priced and approved before any credit is used.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to rank model variants and hunt down API offers for a specific task, estimate real billed cost, audit n8n/Make automations for overpay, missing fallbacks and deprecated models, and plan or run evaluation and canary suites on the user's own examples. It also supports price comparison, custom reseller channels with measured per-call cost, and non-LLM capabilities such as web search and speech-to-text.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to query live AI model pricing, compare providers, and calculate token workload costs from current published prices.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables real-time access to LLM pricing, benchmarks, deprecation alerts, and cost optimization for over 30 models across 8 providers, allowing AI agents to make cost-effective model selections.
      -

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct purpose: single model lookup, chat completion, filtered catalog listing, and price comparison. However, list_models and compare_prices both surface pricing information and could be confused by an agent deciding which to call for cost data, and the bare name 'model' is less self-explanatory than the others.

    Naming Consistency3/5

    Two tools follow a verb_noun pattern (list_models, compare_prices) while the other two are bare nouns (model, chat), and 'model' is a particularly vague name for a getter. The set is readable but mixes conventions without a clear rule.

    Tool Count4/5

    Four tools is a tight, purposeful set for an LLM gateway: discovery, pricing comparison, and chat execution all earn their place. It sits at the thin end of the ideal range but nothing is redundant.

    Completeness3/5

    Core workflows (find a model, compare cost, run a chat) are covered with no dead ends, but obvious gateway operations are absent — no way to check account balance/credits or limits despite cost-returning chat, and no embeddings or streaming-specific entry point. Agents can work around these but will hit the gap on billing or non-chat use cases.