
### Every subnet, metagraphed.
**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, 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.
[](https://metagraph.sh)
[](https://api.metagraph.sh/mcp)
[](https://registry.modelcontextprotocol.io/v0/servers?search=metagraphed)
[](https://mcp.so/server/metagraphed---bittensor-subnet-registry/JSONbored)
[](https://smithery.ai/servers/metagraphed/metagraphed)
[](https://www.npmjs.com/package/@jsonbored/metagraphed)
[](https://pypi.org/project/metagraphed/)
[](./LICENSE)
**[Website](https://metagraph.sh)** · [API](https://api.metagraph.sh) · [OpenAPI](https://api.metagraph.sh/metagraph/openapi.json) · [MCP](https://api.metagraph.sh/mcp) · [Agent docs](https://api.metagraph.sh/llms.txt) · [Agent workflows](https://api.metagraph.sh/agent-workflows.md) · [Feeds](https://api.metagraph.sh/api/v1/feeds/registry) · [npm](https://www.npmjs.com/package/@jsonbored/metagraphed) · [PyPI](https://pypi.org/project/metagraphed/)
---
## What it is
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](https://metagraph.sh)**. The API is served from **`https://api.metagraph.sh`** (REST under `/api/v1`, artifacts under `/metagraph`).
## Quickstart
Three ways to use Metagraphed. Pick one.
#### 🤖 AI agent (MCP)
Agent-native, account-authenticated, Streamable-HTTP. Sign-in is free. 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.
```bash
claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp
```