AISIX AI Gateway runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 22 Oct 2026.
Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint
We read the source, 3 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
"169.254.169.254",
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch AISIX AI Gateway and you get told the day something new turns up.
Self-hosted gateway aggregating upstream MCP servers behind one authenticated HTTP endpoint.
MCP gateway aggregating MCP servers and OpenAPI/Swagger REST APIs behind one MCP endpoint
Self-hosted MCP gateway: connect 1,178 apps once and use them from any AI agent.
MCP gateway federating 22 biomedical MCP servers behind one endpoint: gnomAD, ClinVar, HPO, VEP.
Permission gateway for AI agents: scoped MCP endpoints over 27 services, audited and revocable.
AuthzX MCP Gateway — policy-enforcing proxy between AI agents and MCP servers
One remote MCP connection: 39,500+ ranked MCP servers, agent delegation, hosted tool gateway.
Self-hosted Anytype MCP server: the full Anytype API as an always-on Docker + HTTP endpoint.
Answers built from our own checks of this server.