MCP-native release confidence control plane for web apps
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":"blop-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.
# blop — The MCP-Native Release Confidence Control Plane Most AI testing tools can click through pages. Teams still do not know whether they should ship. **blop** turns browser execution into **release decisions** by combining business-critical journey context, evidence-heavy QA runs, and risk governance in one MCP-native control plane. You do not write test code. You ask in chat, then ship with auditable evidence, prioritized risk, and a clear go/no-go recommendation. Compatible MCP clients: **Cursor**, **Claude Code**, and other clients that support MCP tool/resource workflows. ## Quick Navigation - [Product thesis](#product-thesis) - [What it actually does](#what-does-it-actually-do) - [Why blop vs generic AI testing agents](#why-blop-vs-generic-ai-testing-agents) - [Before you start](#before-you-start--what-youll-need) - [Install](#installation--step-by-step) - [Release packaging](#release-packaging) - [Configure and connect](#configure-and-connect-blop) - [Production setup](#production-setup-local-managed-stdio) - [5-minute quickstart](#your-first-mcp-native-run-in-5-minutes) - [Business-context QA scenarios](#real-world-testing-scenarios-for-b2b-saas) - [MCP resources + v2 surface](#mcp-resources--v2-surface-summary) - [Troubleshooting](#troubleshooting) - [Full tool reference](#full-tool-reference) --- ## Product thesis - **Core belief:** teams do not have a "generate more tests" problem; they have a **release confidence** problem. - **What competitors miss:** bug detection without business weighting creates noisy output and weak ship/no-ship decisions. - **What blop uniquely does:** connect context graphs, regression evidence, incident patterns, and telemetry into a single risk narrative that leaders can act on. --- ## What does it actually do? 1. **Captures context** with inventory + graph resources agents can read cheaply 2. **Discovers and records** business-critical flows from that context 3. **Replays** flows asynchronously to catch regress…
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.