Read your MCP config before you run the server: zero-dependency policy lint, diff and CI gate.
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-policy-lint","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-policy-lint [](https://github.com/ravenkernel/mcp-policy-lint/actions/workflows/ci.yml) [](https://github.com/ravenkernel/mcp-policy-lint/blob/main/LICENSE) [](https://pypi.org/project/mcp-policy-lint/) **English** | [简体中文](README.zh-CN.md) Turn `mcp.json` into a readable, testable, PR-blocking permission policy — **before** you run any MCP server. Local, zero dependencies, no model key, no Docker. ```bash pip install mcp-policy-lint # installs the mcp-policy-lint command mcp-policy-lint demo # 30 seconds, no network, no API key, no Docker # from a checkout instead: pip install -e . ``` ``` mcp-policy-lint demo — 2 servers scanned, 6 findings no network, no API key, no Docker (vs sample baseline: 3 drift rows — run `mcp-policy-lint diff` to inspect) mcp-policy-lint 0.2.0 — 6 findings ERROR POL003 remote /mcpServers/remote/url Plaintext HTTP to a remote endpoint http://api.example.com/mcp has no TLS, so tool descriptions and responses can be altered in transit fix: Use https:// and confirm the authentication settings ERROR POL001 shell /mcpServers/shell/command stdio command can start a shell shell runs its arguments through sh, so it can execute arbitrary commands fix: Call a concrete executable directly instead of assembling a command with -c ERROR POL002 shell /mcpServers/shell/env/AWS_SECRET_ACCESS_KEY Likely real credential in config AWS_SECRET_ACCESS_KEY is not a placeholder; it can leak through logs or travel with the repository fix: Reference an environment variable or a secret manager; never put the value in mcp.json ERROR POL004 shell /mcpServers/shell/roots/0 r…
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.