Router-MCP
Related Servers
Alternatives to Router-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a governance gateway for LLM and agent traffic via MCP, blocking prompt injection, redacting PII, enforcing per-tenant token budgets, and caching repeat questions semantically. Enables AI agents to route model calls through the same guardrails instead of calling providers directly.MIT
- AlicenseNot gradedqualityDmaintenanceA configurable MCP server that intelligently routes natural language queries to the appropriate microservice endpoint based on user-defined service configurations.4 npmMIT
- FlicenseBqualityBmaintenanceProvides deterministic intent routing and safety gating for multi-agent systems, enforcing P0 critical word detection, mutually exclusive hard rules (MX-1/2/3), and a permission matrix as pure functions via four MCP tools.4-
- AlicenseNot gradedqualityBmaintenanceEnables natural language interaction with complex computer vision workflows such as auto-labeling, class mapping, and embedding selection through an LLM-agnostic MCP orchestration layer.2MIT
- FlicenseNot gradedqualityDmaintenanceEnterprise-grade intent routing gateway implementing the Model Context Protocol (MCP) spec, optimizing context by routing queries to specialized sub-nodes to reduce token overhead by 85% with negligible latency overhead.-
- AlicenseNot gradedqualityCmaintenanceUniversal MCP router and gateway that bridges LLM agents to OpenAPI, GraphQL, and AWS Lambda services with ISO/IEC 42001 AI governance, RBAC, PII redaction, semantic tool routing, and a web dashboard.MIT
TDQS
Scored across 7 tools
Most tools have distinct purposes: clarify_query, explain_route, route_query, and validate_route target different stages of query processing, while list_capabilities and validate_capabilities focus on server capabilities. However, plan_task is somewhat vague and could overlap with route_query or clarify_query in function.
All tool names follow a consistent verb_noun pattern using snake_case, such as clarify_query, explain_route, and list_capabilities. There are no deviations in naming conventions, making the set predictable and readable.
With 7 tools, the count is well-scoped for a router server, covering query clarification, routing, validation, and capability management without being overwhelming. Each tool appears to serve a specific role in the routing workflow.
The tool set covers key aspects of routing: query clarification, route explanation, planning, routing, and validation, along with capability listing and validation. A minor gap might be the lack of tools for dynamic route updates or error handling, but core operations are present.