A local MCP server that starts and watches Mindcraft research runs.
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":"mindcraft-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.
# mindcraft-mcp The local MCP server of Mindcraft by Latency Labs. It runs on your machine and connects Codex or Claude Code to your Mindcraft account. Your assistant can then prepare your own repository and start, watch and steer research campaigns on it. The server holds only your API URL and your personal API token. The Mindcraft service keeps all campaign state. ## Setup The procedure needs `uv`. It supplies Python by itself. 1. If `uv` is not installed, install it: `curl -LsSf https://astral.sh/uv/install.sh | sh`. 2. Register the server in your client. - Claude Code: `claude mcp add mindcraft --scope user -- uvx mindcraft-mcp@latest` - Codex: `codex mcp add mindcraft -- uvx mindcraft-mcp@latest` 3. Ask the client: "Show my Mindcraft account." A browser page opens. Sign in with Google, then click **Connect**. The first sign-in stores the token in `~/.config/mindcraft/credentials.json` (mode 0600). If no browser can open, the call gives a URL to open on another device. Call the tool again after you approve the request. Caution: Click **Connect** only for a command that you started on your own machine. Terminal commands: | Command | Purpose | | --- | --- | | `uvx mindcraft-mcp setup` | Sign in and register the server in each client on your `PATH`. | | `uvx mindcraft-mcp setup --no-browser` | Sign in without a browser. Open the URL on another device and type the code. | | `uvx mindcraft-mcp logout` | Revoke the token and delete the credentials file. | | `uvx mindcraft-mcp --version` | Show the package version and the schema version. | ## First campaign 1. Ask your operator for a campaign spend limit on your account. Without a limit, the checks stop with `LIMIT_REQUIRED`. 2. On the website, save the secret values that your training needs at `/settings/secrets`. Add model keys and the GitHub connection for private repositories at `/settings/connections`. 3. Ask the assistant to prepare your repository for Mindcraft. The assistant r…
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.