+ Miners and contributors use the local MCP package. Metadata stays on your machine; private + scoreability and blockers appear only in authenticated MCP/API responses. +
+npx — see{" "}
+ Quickstart.
+ + Wire the same tools into Codex, Claude Desktop, or Cursor via{" "} + MCP client setup. Signed-in miners can also use the{" "} + Workbench and Miner dashboard{" "} + in the control panel. +
+ ++ Maintainers install the GitHub App, configure per-repo policy, preview what could appear on + a confirmed-miner PR, then pull context on demand. +
++ The signed-in Maintainer console and{" "} + Repos tab surface the same preview diff when live data is + available. +
++ Deeper workflow: Maintainer workflow. Privacy + rules: Privacy & security. +
+ +
+ Repo owners care about registration readiness and sensible .gittensor.yml{" "}
+ configuration before promoting labels or maintainer-cut policy.
+
+ Readiness is separate from upstream drift: a repo can look ready while Gittensor rules are + stale. Check Upstream drift when you change scoring + assumptions. +
+ ++ Operators watch deployment health, product usage, value rollups, and upstream drift across + installations. These surfaces are private and authenticated — never mirrored to public + GitHub comments. +
+
+ Operator dashboard — backed by{" "}
+ GET /v1/app/operator-dashboard.
+
+ When drift is not current, treat MCP and API responses as tied to the printed
+ ruleset version. See Upstream drift for semantics.
+
+ Public GitHub output must never include wallets, hotkeys, payout or reward estimates, raw + trust scores, public score estimates, private reviewability details, or farming language. + Private MCP, API, and control-panel surfaces may show authenticated scoreability, blockers, + projections, and evidence — framed as guidance, not guaranteed outcomes. +
+Print a config snippet for your editor of choice and paste it in. See{" "} - MCP client setup for the details. + MCP client setup for the details. For the full miner path + (plan → preflight → packet) and other roles, see{" "} + Beta onboarding.