How do I install Metagraphed — Bittensor Subnet Operational Registry?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Metagraphed — Bittensor Subnet Operational Registry need an API key?

No required environment variable is listed on this record.

What transport does Metagraphed — Bittensor Subnet Operational Registry use?

Metagraphed — Bittensor Subnet Operational Registry is reached over HTTP.

When was Metagraphed — Bittensor Subnet Operational Registry last checked?

Last checked 2026-11-10. Live operational + integration registry for Bittensor subnets: APIs, schemas, health.

Metagraphed — Bittensor Subnet Operational R MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://api.metagraph.sh/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.jsonbored-metagraphed https://api.metagraph.sh/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.jsonbored-metagraphed": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://api.metagraph.sh/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.3.0
License

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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

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:

	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

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

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

Resource	URL
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	`` — 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

root SN0 — chain-rpc · site · docs · repo
Apex SN1 · site · docs · repo
DSperse SN2 — verifiable-oracles zkml · site · docs · repo
Templar SN3 — decentralized-training tournament · site · docs · repo
Targon SN4 · site · docs · repo
Hone SN5 · site · repo
Numinous SN6 — forecasting openapi subnet-api · site · docs · repo
— · · ·

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.

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.

Metagraphed — Bittensor Subnet Operational Registry

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Metagraphed — Bittensor Subnet Operational Registry?

Does Metagraphed — Bittensor Subnet Operational Registry need an API key?

What transport does Metagraphed — Bittensor Subnet Operational Registry use?

When was Metagraphed — Bittensor Subnet Operational Registry last checked?

Documentation

Every subnet, metagraphed.

What it is

Quickstart

🤖 AI agent (MCP)

📦 Typed client

🌐 REST

For agents

This repo

Contributing

Subnet catalog

Related

License