yuntu-mcp-server
Related Servers
Alternatives to yuntu-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to discover and use free LLM chat routes and models through an OpenAI-compatible gateway, including provider health, capacity, and failover.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to discover and use pooled free LLM chat routes and models through an OpenAI-compatible gateway with automatic failover across enabled providers.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible applications to interact with local and cloud-hosted LLM models for model management, text generation, chat, embeddings, and web search/fetch.882 npmAGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover and inspect available open models, estimate token costs, and run chat completions through an OpenAI-compatible inference endpoint, with optional bearer-key authentication for billed calls.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables chat, document search (RAG), and a declarative SQL tool builder over MCP so any client can use these capabilities.62 npm1AGPL 3.0
- FlicenseAqualityDmaintenanceUnified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.222 npm-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: chat_completion handles LLM interactions, get_balance checks token quota, and list_models shows available models. No overlap or ambiguity between them.
All three tool names follow a consistent verb_noun pattern in snake_case: chat_completion, get_balance, list_models. The naming is uniform and predictable.
With only 3 tools, the surface is minimal but appropriate for a straightforward LLM gateway. It covers the essential actions (use model, check balance, list models) without unnecessary bloat, though a few more (e.g., channel management) could be expected.
The tool set covers the core user-facing operations for an LLM gateway: chatting, checking balance, and discovering models. It lacks administrative features like managing channels, but for the apparent consumer-focused scope, these are reasonable gaps.