Skip to content
Gittensory
MCP v0.4.0 · deterministic base agent

Mine Gittensor like an engineer.Not like a bot.

Gittensory is the deterministic base-agent layer for Gittensor OSS contribution mining. Plan better work, preflight branches, and keep maintainer review surfaces quiet.

Install MCP →Read the docs
npm · @jsonbored/gittensory-mcpv0.4.0
npm i -g @jsonbored/gittensory-mcp@latest
Browse the API →For coding agents →
~ gittensory-mcp
$
MCP package
@jsonbored/gittensory-mcp v0.4.0
API
unknown
Last checked
—
Upstream drift
monitored
What it gives you

One base layer, three audiences, no surprises.

For miners

Find the next move, clear queue pressure, and ship a packet that won't get flagged.

  • plan-next-work
  • preflight-branch
  • explain-blockers
  • prepare-pr-packet
Open guide →
For maintainers

Confirmed-miner context without check noise. One sticky comment, one label, on demand.

  • @gittensory help
  • preflight
  • miner-context
  • duplicate-check
Open guide →
For coding agents

Deterministic tool schemas your agent can actually plan against. Metadata only.

  • stdio MCP
  • remote MCP
  • structured tools
  • Codex · Claude · Cursor
Open guide →
Scoreability, explained

See the upside before you spend a commit on it.

Every analysis returns five scenarios — current, underlying, clean-gate, after-pending-merges, best-reasonable. Estimates only, never guarantees, never raw trust scores.

scoreability
0.42
Current (gated)

Estimates only. Gittensory never shows raw trust scores or promises payouts.

  1. 01 · Current (gated)

    What the subnet would score right now. Blockers like unsquashed commits and a missing linked issue gate the upside.

  2. 02 · Underlying potential

    What the diff is actually worth on signal alone — once the gates are removed. Estimated only, never a guarantee.

  3. 03 · After clean-gate

    Project the score after the branch is squashed, rebased, and the open-PR queue is cleared. The biggest single move for most miners.

  4. 04 · After linked-issue fix

    Add a linked issue from the upstream backlog. Best reasonable case — every other signal stays where it is today.

Stays quiet on PRs

Private intelligence. Public composure.

No always-on check runs. No score numbers in the public thread. One sticky comment for confirmed miners, and a configured label — that's it.

Before — generic mining bot
  • lint / eslintfail
  • ci / unitfail
  • ci / integrationpending
  • gittensor-scorer / previewfail
  • gittensor-scorer / blockerswarn
  • subnet-bot / advisoryfail
  • subnet-bot / nudgewarn
some-mining-bot

Score: 0.42 (gated). Blockers: unsquashed-commits, missing-issue-link. Estimated reward: 0.0031 TAO.

After — Gittensory
  • lint / eslintpass
  • ci / unitpass
gittensory[bot]

Confirmed miner. Preflight: ready. One linked issue · one squashed commit. Maintainer packet available on request.

gittensor:confirmed-miner
Capabilities

A static base layer for moving work.

Branch analysis
Metadata-only inputs yield lane context, scoreability scenarios, and ranked next actions.
Scoreability
Current, clean-gate, after-pending-merges, linked-issue-fixed, best-reasonable. Estimates only — never guarantees.
Upstream drift
Versioned snapshots of the Gittensor source and ruleset flag stale assumptions before they break your plan.
Decision pack
Canonical private payload per miner: official stats, outcome history, lane context, repo targets, freshness, provenance.
Maintainer packets
Reviewability and readiness reports for a PR. Confirmed-miner context. One sticky comment, one label.
Repo readiness
Registration readiness, Gittensor config recommendation, label policy, settings preview, intake health.
Public / private boundary

Private context for you. Quiet output for the repo.

  • MCP transmits metadata only — never source code.
  • No PAT input. CLI uses GitHub Device Flow; session tokens are Gittensory-issued.
  • No wallet, hotkey, or trust-score surfaces.
  • Confirmed-miner PRs get at most one sanitized sticky comment and a configured label.
  • Maintainer commands return packets to the maintainer, not to the public PR.
Read the privacy posture →
  • Public-safe by default
  • Metadata-only, never source
  • No PAT input — Device Flow only
  • Private intelligence stays private
Get started

Wire it into your client in under a minute.

Miners use the CLI. Coding agents wire the MCP via stdio. Same package, two starting points.

terminal · bash
npm i -g @jsonbored/gittensory-mcp@latest
gittensory-mcp login
gittensory-mcp analyze-branch --login your-login --json
Install the MCP
npm · @jsonbored/gittensory-mcpv0.4.0
npm i -g @jsonbored/gittensory-mcp@latest
gittensory-mcp login
gittensory-mcp analyze-branch --login your-login --json
Read the docs
Quickstart →API referenceConfigure Claude / Cursor / Codex
Ready when you are

Skip the noise. Plan the work.

Install the MCP, run an analysis, and see the next move with five scoreability scenarios — no PATs, no source upload, no public score numbers.

Install MCP →Open workbench