Hosted · self-custody
I never touch
your keys.
I'm BittensorMCP. I turn the Bittensor chain into tools your AI can call — read balances and prices, stake, move TAO. I'm hosted, so you have no node to run. And I'm self-custody: I build every transaction, but only you can sign it.
Self-custody by design
I can move nothing without you.
I build
You call a write tool. I assemble the exact on-chain transaction and hand it straight back to you, unsigned.
You sign
Your wallet signs it locally with your coldkey — in your browser extension or your agent's own process. The key stays with you.
I submit
I check the signature is really yours, then broadcast it. All I ever saw was the signature. Never the key.
No custody, no deposits, no wallet held on your behalf. Your private key and recovery phrase never reach me — and there's no code path anywhere in me that would accept them.
Reads are free
Balances, portfolios, subnets, validators, live Alpha prices, swap simulation. No subscription, no card — connect and read.
Writes stay yours
Stake, transfer, run a validator, register or own a subnet. 0.1 TAO a month, paid straight from your wallet, every extrinsic signed by you.
Every read is real
I stamp each response with the block it was read at. Your agent works from live chain state — never a number I made up.
Live in a minute.
- 01
Connect
Sign a one-time challenge at /connect with your Bittensor coldkey. No password, no email, one signature.
- 02
Paste
Drop the config into Claude Desktop, Cursor, or any MCP client. Reads work immediately.
- 03
Activate, only if you want writes
Pay 0.1 TAO from your wallet in one click to unlock staking and transfers. Skip it entirely if you only need reads.
Building an agent to run this end to end? The complete, runnable onboarding (wallet, auth, billing, every tool) is in llms.txt. TypeScript signing helper: @bittensormcp/sign.
Straight answers.
- Is my private key ever at risk?
- No. I compose transactions, but I can't sign them. Signing happens on your machine, with your key. All I ever receive back is the finished signature — never the key, never your recovery phrase. There's no code path in me that accepts one.
- What does it cost?
- Reads are free, forever. To write, you keep a subscription topped up: 0.1 TAO a month, paid from your own wallet — no card, no signup. Send more to add more time (0.2 TAO buys 60 days). Stop whenever you like by not renewing.
- Is the data actually live?
- Yes. I stamp every response with the exact block I read it at. If the chain is unreachable I hand you an error, not a stale or invented number. Your agent works from real chain state, never a guess.
- Which clients work?
- Anything that speaks MCP: Claude Desktop, Cursor, Claude Code, or your own calls. Clients without native Streamable HTTP can use the mcp-remote bridge. If your client's connector UI only offers OAuth with no field for a static token, that works too — I run a small OAuth 2.1 layer that signs you in the same way. No wallet extension? Sign from the terminal with btcli at /connect/manual.
- Can my agent set this up for me?
- Yes. Point your AI agent at bittensormcp.com/llms.txt and it can do the whole thing itself: create a wallet, walk you through funding it, connect to me, and start. Free by default — it only activates Pro if you ask for writes.
Give your agent
the whole chain.
Free reads, forever. Self-custody writes for 0.1 TAO a month. Your keys stay yours.