Live session wrapper composing mcp-doctor's registration gate, mcp-fuzz's latency gate, and mcp-reality-check's correctness gate into one call site for a real MCP agent session.
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-trust-check","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-trust-check One GitHub Action that runs the full MCP trust & safety trilogy — [`mcp-doctor`](https://github.com/vishalhabib99/mcp-doctor), [`mcp-fuzz`](https://github.com/vishalhabib99/mcp-fuzz), [`mcp-reality-check`](https://github.com/vishalhabib99/mcp-reality-check) — against an [MCP](https://modelcontextprotocol.io) server and posts one combined score, instead of three separate installs and three separate reports. Also a Python package (`pip install mcp-trust-check`) doing the same job for a live agent session instead of a CI run — see [Live session wrapper](#live-session-wrapper) below. Each of the three tools already works standalone and does something the other two structurally can't: - **mcp-doctor** reads the server's source and checks spec conformance/security/documentation — no server execution needed. - **mcp-fuzz** actually launches the server and calls every tool with schema-derived inputs, checking crash resilience, latency, response size, and (opt-in) concurrency and resource-lifecycle correctness. - **mcp-reality-check** also launches the server, but checks whether a tool's *successful* response is actually trustworthy — no disguised refusals, no empty content, no output that quietly ignores its own schema. None of them use an LLM judge anywhere — every check here is deterministic and reproducible, same as the tools it wraps. ## Demo 35 seconds, live run against the official MCP reference server — real output, no cherry-picking: 86%/B code quality, 100%/A crash resilience, 100%/A output fidelity, 95%/A combined. <video src="docs/demo.mp4" controls width="100%"></video> ## Use Static-only — zero extra config, works on any checked-out repo: ```yaml - uses: actions/checkout@v4 - uses: vishalhabib99/mcp-trust-check@v1 with: path: . ``` Full trilogy — also add `run` with the command that actually starts your server over stdio: ```yaml - uses: actions/checkout@v4 - uses: vishalhabib99/mcp-trust-check@v1 with: path: . run…
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.