A central server for MCP servers
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":"argus-mcp","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.
<!-- markdownlint-disable first-line-heading no-inline-html no-emphasis-as-heading --> <picture> <img src="./docs/.images/argus-mcp-logo.png" alt="Argus MCP" width="420"/> </picture> [][pypi] [][pypi] [][pypi] [![PyPI version][pypi-img]][pypi] [![Docker Hub pulls][docker-img]][docker] [![GHCR][ghcr-img]][ghcr] [![License: GPL-3.0][license-img]][license] [![Build status][ci-img]][ci] [](https://github.com/diaz3618/argus-mcp/actions/workflows/semgrep.yml) # Argus MCP - a single gateway guarding your MCP servers **Connect any MCP client to all your MCP servers through a single server.** Argus MCP is a central gateway and management platform for the [Model Context Protocol](https://modelcontextprotocol.io). Rather than configure each AI client to talk to each MCP server individually, point your clients at Argus and let it handle the rest - aggregating capabilities, routing tool calls, managing connections, and securing everything behind one endpoint. <picture> <img src="./docs/.images/argus-mcp-diagram.png" alt="Argus MCP architecture diagram" style="padding: 20px 0"/> </picture> --- <table> <tr> <td width="50%"> ## Why use Argus MCP? - **One endpoint, many backends:** MCP clients connect to one Argus address - Argus aggregates tools, resources, and prompts from all your backend servers. - **Stdio isolation:** Run stdio MCP servers in isolated Docker containers, or deploy them on Kubernetes. - **Any transport:** Backends can be local stdio processes, remote SSE endpoints, or Streamable HTTP servers. Argus works with all three. - **Secure by default:** JWT/OIDC authentication, RBAC authorization, encrypted secret storage, and automatic log redaction. - **Live managemen…
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.