Per-agent scoped MCP tool proxy with credential isolation and audit logging
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":"scoped-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.
# scoped-mcp [](https://claude.ai/code) [](https://github.com/TadMSTR/scoped-mcp/actions/workflows/ci.yml) [](https://pypi.org/project/scoped-mcp/) [](https://pypi.org/project/scoped-mcp/) [](https://opensource.org/licenses/MIT) Per-agent scoped MCP tool proxy. One server process per agent — loads only the tools that agent is allowed to use, enforces resource boundaries between agents, holds credentials so agents never see them, and logs every tool call to a structured audit trail. --- ## The Problem Multi-agent setups (Claude Code subagents, parallel workers, role-based agents) share the same MCP servers. Every agent sees every tool. Every agent holds credentials. Agent A can read Agent B's data. Audit logging is fragmented across a dozen server processes. Existing solutions solve pieces: - **Aggregation gateways** — combine servers, no scoping - **Access control proxies** — filter tools per agent, no resource scoping - **Credential proxies** — isolate credentials, no tool management - **Enterprise gateways** — governance and auth, but cloud and team-oriented None combine all four: **tool filtering + resource scoping + credential isolation + audit logging**. scoped-mcp was built using the same multi-agent pattern it's designed to secure — a research agent evaluated the problem space, a dev agent implemented the code, each with scoped access to only the resources it needed. It runs in production as part of [homelab-agent](https://github.com/TadMSTR/homelab-agent), a self-hosted Claude Code platform with purpose-built agents for different infrastructure domains. --- ## …
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.