Skip to main content
Glama

Related Servers

Alternatives to aiMCPGate

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Self-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.
      1
      213
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Local-first MCP proxy with BM25 tool discovery, quarantine security, Docker isolation, OAuth support, activity logging, and web UI. Routes multiple upstream MCP servers through a single endpoint.
      9
      407
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP Gateway that aggregates multiple upstream MCP servers into a single endpoint with persistent connections, tool registry, and authentication.
      33 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Fronts many downstream MCP servers through one session, presenting a unified tool namespace with collision resolution, fleet-wide allow/deny/hide policy, per-tool rate limits, centralized audit logging, Prometheus metrics, and bearer-key auth at the edge. Supports both stdio drop-in and Streamable HTTP deployment so agents point at a single endpoint instead of N servers.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A zero-dependency MCP gateway: host your own tools, forward and curate tools from other MCP servers, expose them leanly to cut agent token cost, and gate every call through your own policy hooks before it runs.
      4
      18 npm
      38
      MIT

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve completely different purposes: echo returns input text, ping returns a fixed health response. No ambiguity.

    Naming Consistency5/5

    Both tools follow the same pattern: prefix 'demo-echo__' followed by a verb. The naming is uniform and predictable.

    Tool Count4/5

    With only 2 tools, the set is minimal but appropriate for a simple demonstration server. It covers the core functionality without being overly sparse.

    Completeness5/5

    For the stated purpose of a demo echo server, the tools provide exactly what is needed: echo text and health check. No obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues