Back to Directory/Other

metagraphed — Bittensor subnet operational registry

Live operational + integration registry for Bittensor subnets: APIs, schemas, health.

OtherTypeScriptv1.3.0
View on GitHub

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.

Website MCP MCP Registry mcp.so smithery badge npm PyPI License: AGPL-3.0

Website  ·  API  ·  OpenAPI  ·  MCP  ·  Agent docs  ·  Agent workflows  ·  Feeds  ·  npm  ·  PyPI

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. 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.

claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp
Other clients — Cursor, VS Code, Windsurf, Zed, ChatGPT, or anything speaking MCP

Add an MCP server with url https://api.metagraph.sh/mcp and transport streamable-http, then complete the client's OAuth sign-in prompt. For automation or clients without OAuth support, send Authorization: Bearer <mg_api_key> using an issued API key. Missing or invalid credentials receive a 401 with the sign-in metadata. OAuth metadata, registration and the server card remain public.

{
  "mcpServers": {
    "metagraphed": {
      "type": "streamable-http",
      "url": "https://api.metagraph.sh/mcp"
    }
  }
}

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:

toolsanswers
🔍 Discoversearch_subnets · semantic_search · find_subnets_by_capability · find_subnet_for_taskwhich subnet does the thing I need
🩺 Healthget_subnet_health · get_self_health · list_endpoints · get_best_rpc_endpointis it up, and which endpoint should I hit
🔌 Integratelist_subnet_apis · get_api_schema · how_do_i_call · verify_integrationwhat do I send it, and did it work
📈 Economicsget_subnet_economics · get_subnet_trajectory · get_subnet_yield · compare_subnetsemission, alpha, yield, and how it's trending
⛓️ Chainget_block · list_extrinsics · get_subnet_metagraph · get_neuronraw chain state, chain-direct
👛 Walletsget_account · get_account_events · get_account_subnets · get_account_portfoliowhat one account does across the network
💬 Grounded Q&Aaska cited answer over the whole registry

All tools remain available through a four-tool discovery catalog. The server card links the complete capabilities; common-tool and full-catalog profiles are also available.

For a tighter chat-context budget, configure the endpoint as https://api.metagraph.sh/mcp?search_page_size=1 (or 2). search_tools then returns at most one (or two) complete definitions per page, instead of the default three. Follow next_cursor with the same query to reach every match. Smaller pages trade additional discovery calls for less context per response; they do not shrink individual schemas or tool results. Exact-name search returns just the requested definition. The default catalog remains four tools, and /mcp/core and /mcp?catalog=full retain their existing listings and capabilities.

📦 Typed client

Generated from the OpenAPI contract, published with provenance.

npm i @jsonbored/metagraphed   # JS/TS
pip install metagraphed        # Python
🌐 REST

Stable JSON envelope { ok, data, meta, error }. OpenAPI at /metagraph/openapi.json.

curl https://api.metagraph.sh/api/v1/subnets
Legacy query compatibility

Existing GraphQL clients and the MCP query_graphql tool remain supported at /api/v1/graphql. POST executes a query; GET returns the SDL, introspection remains available, and existing subscriptions remain supported. New integrations should use MCP tools or the REST/OpenAPI contract. The website editor has been retired; see legacy query compatibility.

For agents

ResourceURL
Copyable agent prompt/agent.md
Agent workflows/agent-workflows.md
Machine index/llms.txt
Drop-in skill/skills/bittensor/SKILL.md — or gh skill install JSONbored/metagraphed bittensor
Resources index/metagraph/agent-resources.json
Content feeds/api/v1/feeds/registry — registry changes + incidents, as RSS / Atom / JSON Feed; /api/v1/feeds/gaps for ranked coverage gaps (per-subnet at /api/v1/feeds/subnets/{netuid})
Embeddable badge![metagraphed](https://api.metagraph.sh/api/v1/subnets/{netuid}/badge.svg) — SVG (also /providers/{slug}/badge.svg); ?metric=uptime for reliability, ?metric=completeness for coverage score, plus ?style=flat-square and ?label=…

This repo

Cloudflare Worker API + Node build scripts. Schema-first: JSON Schema is the canonical contract → OpenAPI → types/clients. Artifacts are deterministic JSON; data refreshes on a schedule to R2/KV.

docs/              product + operating notes (start here)
registry/          subnet overlays, candidates, community submissions
schemas/           canonical JSON Schema components
scripts/           validation, generation, probe, safety
workers/           Cloudflare Worker API routes
public/metagraph/  compact generated artifacts + contracts
generated/         generated TypeScript types + client

Deeper docs: docs/api-stability.md (the /api/v1 contract), docs/curation-playbook.md.

Contributing

Open the repo in a devcontainer-aware tool (VS Code, GitHub Codespaces, the devcontainer CLI) for a zero-setup environment — Node 22 + Playwright's Chromium preinstalled. Issues are labeled good first issue and help wanted — start there.

  • Schema-first edits require npm run build (regenerates openapi.json + types).
  • Community submissions are PR-first: add a surface to exactly one registry/subnets/<slug>.json file (via npm run surface:add; use npm run subnet:new first when that subnet has no file yet), no generated artifacts.

See CONTRIBUTING.md and docs/curation-playbook.md.

Subnet catalog

128 curated subnets — 117 with a site, 46 with docs, 116 with a public repo. Live health, search, and the full list (every active subnet, not just the curated ones) at metagraph.sh; per-subnet JSON at https://api.metagraph.sh/api/v1/subnets/{netuid}. Root (SN0) is base-layer chain infrastructure, listed separately below, not counted as a subnet.

Focus areas: compute 9 · data 7 · defi 6 · inference 6 · language-models 4 · prediction-markets 4 · computer-vision 3 · finance 3 · dashboard 2 · data-artifact 2 · decentralized-training 2 · depin 2

Auto-generated from the curated overlays in registry/subnets/ by scripts/generate-registry-readme-section.ts — enrich a subnet (one PR) and it appears here. Not the live list; browse + monitor everything at metagraph.sh.

Related

  • Frontend — apps/ui/ in this repo (folded in from the standalone metagraphed-ui repo via monorepo consolidation): the web app at metagraph.sh — block explorer, subnet directory, and a non-custodial staking/delegation flow (/delegate). Vite + React 19 + TanStack Start, deployed as its own independent Cloudflare Worker. Holds no subnet data — it renders what this backend serves.

License

The backend (Cloudflare Worker + build pipeline) is AGPL-3.0. The published client SDKs are permissively licensed so you can embed them freely — packages/client (npm) and python/ (PyPI) are Apache-2.0.

© 2026 JSONbored

Setup from the maintainer

This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.

Learn More

MCP vs ACP: What's the Difference Between Agent Protocols?MCP connects an agent to tools and data. ACP connects an editor to an agent. They sound similar and get confused constantly, but the JetBrains-Zed backed ACP and Anthropic's MCP were built to stack on top of each other.Read articlePinterest vs Microsoft Advertising MCP ServersTwo ad platforms shipped MCP servers on the same day, one week ahead of Cannes Lions. Pinterest's is an invite-only alpha; Microsoft's is a broadly available pilot. Neither is indexed in MCPFind's directory yet. Here's the real difference between them.Read articleHome Assistant MCP Server: 4 Options Compared for ClaudeHome Assistant has no vendor-official MCP server, so four community projects fill the gap, each with a different architecture. This guide compares voska/hass-mcp, homeassistant-ai/ha-mcp, achetronic/hass-mcp, and a custom-component option so you can pick the one that matches your setup.Read article