Live operational + integration registry for Bittensor subnets: APIs, schemas, health.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
The open registry and block explorer for Bittensor. All 128 subnets, the APIs and schemas each one publishes, whether those endpoints answered our last probe, and how to call them — as REST, GraphQL, MCP tools and CSV.
Bittensor didn't ship with a map, so we drew one. Every health figure here is probe-derived on a 15-minute cycle; none of it is self-reported.
Website · API · OpenAPI · GraphQL · MCP · Agent docs · Agent workflows · Feeds · npm · PyPI
The native Bittensor metagraph tells you what's happening at the protocol layer. Metagraphed adds the builder-facing layer it lacks: a chain-direct block explorer (its own Rust indexer, no third-party RPC dependency), a registry of every subnet's public interfaces, endpoint health, and machine-readable schemas, and an agent toolkit — 200+ MCP tools, paste-ready OpenAI/Anthropic specs, a drop-in skill — built for integration developers, often reached through their AI agents. A live read-only RPC/WSS proxy and non-custodial, wallet-signed staking/delegation round it out.
Not an official OpenTensor/Bittensor project · not a replacement for the native metagraph · not an alpha/price dashboard · not custodial — staking and delegation are wallet-signed client-side; keys and credentials never touch our backend.
The web UI lives at metagraph.sh. The API is served from https://api.metagraph.sh (REST under /api/v1, artifacts under /metagraph).
Three ways to use Metagraphed. Pick one.
Agent-native, public, read-only, Streamable-HTTP. 200+ tools to explore the chain, discover a subnet, check if it's up, read its economics and metagraph, trace what a wallet does across the network, and learn how to call it.
Add an MCP server with url https://api.metagraph.sh/mcp and transport streamable-http. No API key, no account, read-only.
Ask it things like:
"Which Bittensor subnets have a public API I can call today?" "Is SN64 healthy, and what does its OpenAPI spec look like?" "What changed on subnet 38 last week?" "Which validator should I look at for subnet 19, and what's their take?"
What the tools cover:
| tools | answers | |
|---|---|---|
| 🔍 Discover | search_subnets · semantic_search · find_subnets_by_capability · find_subnet_for_task | which subnet does the thing I need |
| 🩺 Health | get_subnet_health · get_self_health · list_endpoints · get_best_rpc_endpoint | is it up, and which endpoint should I hit |
| 🔌 Integrate | list_subnet_apis · get_api_schema · how_do_i_call · verify_integration | what do I send it, and did it work |
| 📈 Economics | get_subnet_economics · get_subnet_trajectory · get_subnet_yield · compare_subnets | emission, alpha, yield, and how it's trending |
| ⛓️ Chain | get_block · list_extrinsics · get_subnet_metagraph · get_neuron | raw chain state, chain-direct |
| 👛 Wallets | get_account · get_account_events · get_account_subnets · get_account_portfolio | what one account does across the network |
| 💬 Grounded Q&A | ask | a cited answer over the whole registry |
200+ tools total — the full list is in the server card, and a curated 23-tool core profile is available for context-limited agents.
Generated from the OpenAPI contract, published with provenance.
Stable JSON envelope { ok, data, meta, error }. OpenAPI at /metagraph/openapi.json.
Shape one request across the registry — a subnet with its health, surfaces, endpoints, and economics, a provider with its subnets, or the economic opportunity boards. POST to /api/v1/graphql; GET returns the SDL and introspection is enabled.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/metagraphed-bittensor-subnet-operational-registry)<a href="https://allmcps.com/mcp/metagraphed-bittensor-subnet-operational-registry"><img src="https://allmcps.com/api/badge/metagraphed-bittensor-subnet-operational-registry?style=directory" alt="Metagraphed — Bittensor subnet operational registry on AllMCPs" /></a>