BittensorMCP

io.github.btmcpPublished by GitHub account btmcpv1.0.0Updated Oct 24, 2026

Hosted MCP server for live Bittensor chain reads and self-custodial on-chain writes.

VerifiedStreamable HTTPWeb executableDatabasesFinance

Overview

AI-generated overview

Hosted MCP server giving assistants live Bittensor chain reads (balances, subnets, metagraphs, validators) plus self-custodial on-chain writes.

What you can do
  • Read chain data: balances, accounts, blocks, subnet lists and metagraphs, validators, dynamic info and swap simulations
  • Perform on-chain actions: stake and unstake, transfer TAO, register on subnets or root, set weights
  • Sign writes locally through a two-step flow that returns an unsigned payload and intent ID, then broadcasts the returned signature
  • Check premium status and activation requirements
When to use it
Useful when an assistant needs current Bittensor network data, or when you want it to prepare and broadcast staking, transfer or registration extrinsics while your key stays on your own device.
Requirements
Remote Streamable HTTP endpoint; OAuth authentication is declared, and the README shows a bearer JWT obtained via the provider's signing SDK (npm package) plus an Authorization header. Reads are described as free without signup; premium write access requires sending TAO to a treasury address.
Before you install
Write tools move funds and change on-chain state (staking, transfers, registrations, weights) and cannot be undone. Premium activation costs TAO sent to a treasury address. The server receives signed extrinsics and broadcasts them; keep the private key and JWT on your side and verify payloads before signing.

Installation

In SourceWeft

  1. Open BittensorMCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.btmcp%2Fbittensormcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bittensormcp": {
      "type": "http",
      "url": "https://bittensormcp.com/api/mcp"
    }
  }
}

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

bash
npm install @bittensormcp/sign

2. Authenticate (self-custody)

javascript
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:

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

Claude Desktop / Cursor / VS Code:

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

Clients without native Streamable HTTP:

json
{  "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

Source: README.md at commit b95199b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.