Persistent context and governed agent orchestration over MCP
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":"ccc-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.
<p align="center"> <img src="docs/assets/logo.jpg" alt="ccc-mcp logo" width="120"> </p> # ccc-mcp **Let ChatGPT Chat write, test, and review code on your own computer.** [](https://github.com/bruce601080102/ccc-mcp/actions/workflows/ci.yaml) [](https://www.python.org/downloads/) [](docs/en/1-install-and-sign-in.md) [](https://modelcontextprotocol.io/) [](LICENSE) [](docs/en/2-connect-chatgpt.md) [](docs/en/4-workflow.md) [](docs/en/4-workflow.md) ccc-mcp connects ChatGPT Chat to a local coding workspace through MCP, so it can work on an **authorized repository**. Its core idea: **don't take an AI's word that the code works — keep local evidence.** Tests are run by the host, not reported by the agent; every diff, test result and review is saved and resumable, which a chat window can't do on its own. As a bonus, it runs on your existing ChatGPT plan, with no separately metered model API to set up. **ChatGPT-only is the primary workflow.** Codex and Claude Code are optional providers for teams that want to split roles across tools. > [繁體中文 README](README_ZH.md) · [English documentation](docs/en/1-install-and-sign-in.md) ## Watch the demo **1080p · 60 fps ·…
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.