AISIX AI Gateway
OfficialRelated Servers
Alternatives to AISIX AI Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP gateway that exposes a single MCP URL to AI agents and routes tools/resources to many upstream MCP servers behind it.4,605 npmMIT
- FlicenseNot gradedqualityBmaintenanceA FastAPI-based MCP gateway that aggregates multiple MCP servers, applies per-server tool allow/block policies, and re-exposes them as streamable HTTP MCP endpoints. It includes a local LLM safety guard for SQL/PII checks and a request history UI.-
- AlicenseAqualityAmaintenanceA 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.450 npm38MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted workspace MCP gateway that registers MCP servers, stores secrets encrypted, mints agent keys, and shares a unified tool library across multiple AI harnesses.1Apache 2.0
- FlicenseNot gradedqualityAmaintenanceA 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-
- AlicenseNot gradedqualityDmaintenanceMCPGate 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.11 npmApache 2.0
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly distinct by default.
The name 'echo__echo' follows a namespace-style pattern, but with only one tool there is no broader pattern to evaluate. The double underscore is unusual but not inconsistent within the set.
A single echo tool is extremely thin for a server named 'AI Gateway'. The tool count is far below what the domain implies, making the server feel more like a stub than a functional gateway.
The tool surface is severely incomplete for any plausible interpretation of an AI Gateway. It lacks any gateway-related operations such as routing, request handling, model access, or configuration.