MCP.Market

BittensorMCP MCP server

online · 100% uptime
by btmcp·io.github.btmcp/bittensormcp·v1.0.0

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

A90/100grade A
What users say
No reviews yet
Be the first
Safety scan
A90/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed BittensorMCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

BittensorMCP tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 286ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 77 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 90/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How BittensorMCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
90/100
higher than 83% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
226 ms
faster than 59% of 30,031 servers

Install BittensorMCP in Claude Code, Cursor or VS Code

claude mcp add --transport http bittensormcp https://bittensormcp.com/api/mcp
Add to Cursor

What the publisher says

From the BittensorMCP repository's README, as published. We do not edit it. Read it on GitHub

BittensorMCP

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

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 UNSIGNEDPAYLOAD plus intentid, 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

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

License

MIT

Nothing above is checked by us. What we check is on the safety report.

BittensorMCP: common questions

Is BittensorMCP MCP server safe?
Yes, by our scan: it is graded A (90/100). Read the BittensorMCP safety report
How do I install BittensorMCP?
It runs remotely at bittensormcp.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does BittensorMCP need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is BittensorMCP maintained?
The last commit was 78 days ago (2026-08-18). The latest release is v1.0.0.
Is BittensorMCP up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does BittensorMCP compare with other MCP servers?
safety score 90/100 (higher than 83% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 226 ms (faster than 59% of 30,031 servers). Full comparison.