Skip to main content
Glama
ayeyouok

a207-router-mcp

by ayeyouok

Related Servers

Alternatives to a207-router-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      D
      maintenance
      Routes 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      1
      MIT No Attribution
    • A
      license
      Not graded
      quality
      D
      maintenance
      Policy 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.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Governed 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Governance engine for MCP tool calls, providing deterministic rule enforcement to block destructive actions like SQL drops, shell commands, and file system modifications before execution.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      IntentFence 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.
      2
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation3/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing