a207-router-mcp
Related Servers
Alternatives to a207-router-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceRoutes natural language queries to appropriate MCP tools and planners with high-precision semantic matching and safety guardrails. Supports multi-intent detection, task planning, and strict role-based filtering to prevent misexecution or unauthorized access.7-
- AlicenseNot gradedqualityDmaintenanceA governance and control layer for MCP tools that manages tool requests as intents through policy-based approval, queuing, or blocking. It enables secure human oversight and audit trails for consequential agent actions across platforms like Claude Desktop and Cursor.1MIT No Attribution

authensor-mcp-serverofficial
AlicenseNot gradedqualityDmaintenancePolicy enforcement gateway for MCP tool calls, evaluating every tool invocation against declarative YAML policies (allow/deny/escalate-to-human), generating cryptographic hash-chained audit receipts, and including built-in content safety scanning.2MIT
evav-gatewayofficial
AlicenseNot gradedqualityBmaintenanceGoverned MCP gateway that lets AI agents call tools with policy enforcement, prompt-injection screening, a kill-switch, and tamper-evident signed audit logs.Apache 2.0- AlicenseNot gradedqualityDmaintenanceGovernance engine for MCP tool calls, providing deterministic rule enforcement to block destructive actions like SQL drops, shell commands, and file system modifications before execution.2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceIntentFence is an open spend and action policy gate for autonomous AI that evaluates tool call constraints like scope, cost, data-retention, and approval, returning decisions such as safe_to_proceed, needs_review, or denied, and provides an MCP server endpoint at /mcp.2Apache 2.0
TDQS
Scored across 4 tools
Tool purposes are mostly distinct, but check_permission and classify_intent both deal with caller permissions, and extract_slots overlaps with classify_intent's slot output, creating potential confusion about when to call each. Descriptions help clarify the different aspects (permission matrix vs routing vs safety gate vs slot extraction).
All tool names follow a consistent verb_noun pattern with lowercase snake_case: check_permission, check_safety_gate, extract_slots, classify_intent. Predictable and uniform.
With only 4 tools, the server is tightly focused on routing and safety. Each tool covers a distinct aspect of the routing pipeline without redundancy, making the count well-scoped.
The tool set covers the full routing lifecycle: intent classification, slot extraction, permission checking, and safety gating. No obvious missing operations for the stated router purpose; the safety gate includes comprehensive MX-1/MX-2/MX-3 rules.