Enterprise governance middleware for MCP servers: cost attribution, auth, observability, quotas, audit, and policy — composable around the official MCP Python SDK.
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-harness","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-harness **Enterprise governance middleware for MCP servers.** Cost attribution, auth, observability, quotas, audit, and policy — composable around the official [MCP Python SDK](https://github.com/modelcontextprotocol/python-sdk). [](https://github.com/nagenshukla/mcp-harness/actions/workflows/test.yml) [](https://pypi.org/project/mcp-harness/) [](https://pypi.org/project/mcp-harness/) [](LICENSE) --- ## Why this exists Most public MCP servers are toy examples. The gap between *"works on my laptop"* and *"I can ship this to 500 engineers under SOC 2, GDPR, and a Finance team that wants per-business-unit cost allocation"* is enormous — and almost none of that gap is in the protocol. It's in the boring middleware around it. `mcp-harness` **is** that middleware. It doesn't fork the protocol, doesn't reinvent the SDK, and doesn't try to be an agent framework. It's a set of composable decorators and middleware that wrap the official SDK so the resulting server can be safely run inside a company. The headline use case: **your CFO asks who's spending the AI budget, and you can answer by end of week one.** ## Install ```bash pip install mcp-harness # core pipeline (no MCP SDK required) pip install 'mcp-harness[server]' # + the official MCP SDK, to actually serve tools pip install 'mcp-harness[all]' # + OpenTelemetry, Prometheus, tiktoken, JWT ``` The core middleware pipeline has **no hard dependency** on `mcp`, so you can unit-test all your governance behaviour without a transport. Install the `server` extra to run a live server. ## Hello, governed world The same MCP server you'd write anyway, with the governance layer declared once at the top: ```python from mcp_harness…
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.