Standalone MCP gateway — persistent connections to external MCP servers
Until 2026-09-27 this record combined several servers published from one repository. The others now have records of their own: slife-mcp. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-plugin","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-plugin — MCP gateway to external MCP servers **mcp-plugin is a standard [MCP](https://modelcontextprotocol.io) server** that connects to *external* MCP servers — stdio, SSE, or Streamable HTTP — keeps those connections alive, and exposes their tools to a host as one MCP endpoint. It manages everything through MCP itself: add/configure/remove servers, search and load their tools, call them, check status. Any MCP client can drive it. > Status: **Streamable HTTP** transport. Ships with > [Slife](https://github.com/juzcn/slife) as its built-in MCP gateway, but has > **no dependency on it** — usable standalone or from any MCP client. ## Features - **One endpoint, every server** — connect any number of external MCP servers (stdio / SSE / Streamable HTTP), keep the connections alive with auto-reconnect. - **Tools are MCP tools** — server management (`mcp_set`, `mcp_remove`, …), discovery (`mcp_tool_search`), loading (`mcp_tool_load`) and calling all go through the MCP protocol. - **No CLI** — configuration lives in `mcp-plugin.json5` (self-hosted) and the feature surface is 100% MCP tools. - **Tool catalog in memory** — built live from live connections at load and on every reconnect; never persists, never drifts from what the runtime can use. Every tool row keeps its **complete `tools/list` schema** (`{name, description, inputSchema}`) as one compact JSON text column. - **Schema-aware hybrid search** — semantic + FTS5 tool discovery. Keyword indexes name/description/schema text, and the semantic vector is sourced from the full schema alone — so a tool is findable by *what its parameters do*, not just its top-line description. Degrades automatically to keyword when no embedding endpoint is available. - **Standalone config** — path + secret handling mirror the ecosystem conventions (`$VAR` → env → credential store). ## Install Requires **[uv](https://docs.astral.sh/uv)**. ```bash uv tool install --python 3.13 mcp-plugin …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.