mcpField
B
BittensorMCP

BittensorMCP

Remote
bittensormcp.comFinance0Updated 10w ago

About BittensorMCP

BittensorMCP is a hosted MCP server for live Bittensor blockchain queries and on-chain actions. Reads cover chain data, while writes use a signing flow that keeps the private key on the user's device.

Key features

  1. 01Query balances, subnets, and metagraphs
  2. 02Read validator and Alpha price data
  3. 03Perform on-chain actions such as staking and transfers
  4. 04Sign transactions locally with a self-custodial flow

Use cases

  1. 01Check Bittensor balances and subnet data
  2. 02Review validators and Alpha prices
  3. 03Submit staking or transfer actions without sharing the private key

MCP support

Exposes 17 read tools and 17 write actions through a Streamable HTTP endpoint. MCP clients connect to the hosted endpoint; write actions use a two-step flow where signing occurs locally and only the signature is returned.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://bittensormcp.com/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

BittensorMCP

Live, self-custodial Bittensor chain access for AI agents via MCP.

Endpoint SDK

What is BittensorMCP?

BittensorMCP is a hosted Model Context Protocol (MCP) server that gives AI agents live access to the Bittensor blockchain. Connect any MCP client — Claude, Cursor, ChatGPT, VS Code, Windsurf, Zed, Codex — and query balances, subnets, metagraphs, validators, and Alpha prices in real time.

  • Free reads: 17 tools, no signup, no API key
  • Premium writes: 17 on-chain actions (stake, transfer, register, weights) via self-custodial signing
  • One endpoint: https://bittensormcp.com/api/mcp with Streamable HTTP transport

Why self-custodial?

Your private key never leaves your device.

BittensorMCP uses an A2 two-step signing protocol: the server returns an UNSIGNED_PAYLOAD plus intent_id, you sign it locally with your sr25519 key, and only the signature goes back. The server broadcasts the signed extrinsic — it never sees, stores, or handles your private key.

┌─────────────┐      unsigned payload       ┌─────────────┐
│   Your Key  │  <───────────────────────   │  Bittensor  │
│  (local)    │      sign locally           │    MCP      │
│             │  ───────────────────────>   │   Server    │
└─────────────┘      signature only         └──────┬──────┘
                                                   │
                                            broadcast to
                                                   ▼
                                            ┌─────────────┐
                                            │  Bittensor  │
                                            │   Finney    │
                                            └─────────────┘

Quick start

1. Install the SDK
npm install @bittensormcp/sign
2. Authenticate (self-custody)
import { generateWallet, authenticate } from '@bittensormcp/sign';

const wallet = await generateWallet();
const { token } = await authenticate({
  endpoint: 'https://bittensormcp.com',
  ss58: wallet.ss58,
  signer: wallet.sign
});
3. Connect your MCP client

Claude Code:

claude mcp add --transport http bittensormcp \
  https://bittensormcp.com/api/mcp \
  --header "Authorization: Bearer YOUR_JWT"

Claude Desktop / Cursor / VS Code:

{
  "mcpServers": {
    "bittensormcp": {
      "url": "https://bittensormcp.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_JWT" }
    }
  }
}

Clients without native Streamable HTTP:

{
  "mcpServers": {
    "bittensormcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://bittensormcp.com/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer YOUR_JWT" }
    }
  }
}

For step-by-step connection instructions for every client, see the Connect Guide.

Tools at a glance

CategoryCountExamples
Free reads17bittensor_balance, bittensor_account, bittensor_subnet_list, bittensor_subnet_metagraph, bittensor_validators, bittensor_dynamic, bittensor_swap_sim, bittensor_block
Premium writes17bittensor_stake_add, bittensor_stake_remove, bittensor_transfer, bittensor_register, bittensor_weights_set, bittensor_subnet_register, bittensor_root_register

All write tools use the A2 self-custody signing flow. Premium activation requires sending TAO to the treasury address (check bittensor_premium_status for the current rate).

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.