Skip to main content
Glama
naive000

lazy-mcp-router

by naive000

Related Servers

Alternatives to lazy-mcp-router

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCPGate aggregates multiple MCP servers into a single unified endpoint, enabling centralized tool management with granular filtering, automatic namespacing, and observability. Features a real-time web dashboard and optional PostgreSQL-backed audit trails for monitoring and controlling AI tool access across local and remote deployments.
      5 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Runtime security gateway and FastMCP server that protects MCP clients from tool poisoning, prompt injection, and unauthorized tool schema changes through policy enforcement, fail-closed scanning, and human approval gates.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables unified access to multiple MCP backend servers through one local daemon, with curated per-client tool profiles, allow/deny policies, audit logging, and drift protection.
      32 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      A production-ready MCP gateway and control plane that provides credential vault, policy engine, audit logging, and managed runtime for routing tool calls between AI agents and downstream MCP servers.
      58
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP Shield Runtime is a local-first security gateway that controls MCP tool calls with parameter-level policies, approval gates, secret redaction, rate limiting, contract drift detection, and tamper-evident auditing before they reach the upstream MCP server.
      1
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct role: listing backends, searching tools, loading a specific tool, and invoking a tool. No overlap in purpose, and the descriptions clearly differentiate the lifecycle stages.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern in snake_case: list_backends, search_tools, load_tool, call_tool. The naming is uniform and predictable.

    Tool Count5/5

    Four tools is a focused, well-scoped set for a router server. Each tool serves a necessary part of the workflow without redundancy or bloat.

    Completeness4/5

    The core router lifecycle is covered: inspect, search, load, and call. A minor gap is the lack of an explicit unload or backend status operation, but the essential functionality is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues