Audit tool for MCP servers — test protocol compliance, schema quality, and robustness
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-lighthouse","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 Lighthouse Audit tool for [MCP](https://modelcontextprotocol.io) servers. Run 25 automated checks across 5 dimensions and get a compliance score — like Lighthouse, but for your MCP server. ``` MCP Lighthouse — my-server v1.0 Protocol ████████████████████ 100 Schema ██████████████░░░░░░ 70 Robustness ████████████████░░░░ 75 Practices ██████████░░░░░░░░░░ 50 Performance ████████████████████ 100 Overall Score: 83/100 25 checks: 21 passed, 2 warnings, 2 failed ``` ## Why You built an MCP server. It works in Claude Code. But does it: - Return proper JSON-RPC 2.0 responses? - Include `inputSchema` on every tool? - Handle invalid tool names without crashing? - Respond to `initialize` within a reasonable time? MCP Lighthouse tests all of this automatically. ## Install ```bash pip install mcp-lighthouse ``` Or from source: ```bash git clone https://github.com/MakiDevelop/mcp-lighthouse.git cd mcp-lighthouse pip install -e . ``` ## Quick Start ```bash # Audit an MCP server via stdio mcp-lighthouse scan --stdio "python my_server.py" mcp-lighthouse scan --stdio "npx @modelcontextprotocol/server-filesystem /" # Audit a Streamable HTTP endpoint (JSON or SSE responses) mcp-lighthouse scan --http "http://127.0.0.1:8000/mcp" mcp-lighthouse scan --http "https://example.com/mcp" --http-header "Authorization=Bearer token" # Only run specific category mcp-lighthouse scan --stdio "python my_server.py" --category protocol # Export markdown report mcp-lighthouse scan --stdio "python my_server.py" --report audit.md # Use in CI: fail below 80 (critical failures fail by default) mcp-lighthouse scan --stdio "python my_server.py" --fail-under 80 # List all checks mcp-lighthouse list ``` ## Checks (25 total) ### Protocol Compliance (5 checks, 40% weight) — critical | Check | What it tests | |-------|---------------| | `proto-init` | Server responds to `initialize` with valid protocolVersion + capabilities + serverInfo | | `proto-init-…
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.