Coding-agent runtime supervisor, CLI, and Model Context Protocol server
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":"agentdrift-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="web/agentdrift-mark.svg" width="96" alt="AgentDrift interwoven diamond logo"> </p> # agentdrift-mcp — runtime supervisor for autonomous coding agents AgentDrift is the runtime supervisor and circuit breaker for autonomous coding agents. It detects repetitive tool calls and execution spirals, then reports an intervention diagnostic before endless retries consume a token budget. The Python package includes a CLI, local and cloud Model Context Protocol (MCP) servers, and a web telemetry interface. **Python 3.12+** · [PyPI](https://pypi.org/project/agentdrift-mcp/) · [Documentation](https://github.com/sayon999-d/agentdrift#readme) · [Issues](https://github.com/sayon999-d/agentdrift/issues) Project documentation: [architecture](docs/architecture.md) · [API reference](docs/api_reference.md) · [agent instructions](docs/agents_instruction.md) · [configuration](docs/configuration_and_providers.md) · [MCP client matrix](docs/MCP_INTEGRATION_MATRIX.md) · [docs index](docs/README.md). Install the published package with `pip3 install agentdrift-mcp`. It provides the `agentdrift-mcp` MCP server command and the `agentdrift` CLI compatibility alias. MCP clients can launch the local server with `uvx --from agentdrift-mcp agentdrift-mcp`. ## Cross-agent workspace memory Apply `supabase/migrations/20261016_shared_workspace_memory.sql` to the target PostgreSQL/Supabase project. Configure `AGENTDRIFT_SERVICE_TOKEN` on the API and send it as `Authorization: Bearer <token>`. Set `DATABASE_URL` (or a Supabase database URL setting) to persist memory in PostgreSQL; without it, the daemon uses in-memory storage. The MCP-compatible HTTP endpoint is `POST /api/v1/mcp/tools/call`. It accepts JSON-RPC 2.0 `tools/list` and `tools/call` requests. Pass `session_id` in each tool's arguments to identify the repository workspace. The monitoring route is `GET /api/v1/workspace/{session_id}/timeline`. After the existing shared workspace memory migration, apply `su…
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.