PluginBench
MCP Server
Active
AGPL-3.0

metagraphed — Bittensor subnet operational registry MCP Server

io.github.JSONbored/metagraphed

Live operational registry for Bittensor subnets: APIs, schemas, health, and 200+ MCP tools for chain exploration and integration.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the metagraphed — Bittensor subnet operational registry MCP server?

Metagraphed is an open registry and block explorer for Bittensor that provides machine-readable data on all 128 subnets, their public APIs, endpoint health, and schemas. It exposes 200+ MCP tools for AI agents to discover subnets, check health, integrate with APIs, analyze economics, query chain state, and trace wallet activity across the network.

Metagraphed fills a critical gap in Bittensor's developer experience by offering a curated, probe-derived registry of every subnet's operational status, public interfaces, and integration details. Rather than self-reported data, all health metrics are derived from 15-minute probing cycles. It's designed for integration developers and AI agents, accessible via MCP tools, REST, GraphQL, and typed clients (npm/PyPI), with no authentication required for read-only access.

How to install metagraphed — Bittensor subnet operational registry

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "metagraphed": {
      "url": "https://api.metagraph.sh/mcp"
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • search_subnets — Search and discover subnets by name, capability, or semantic query.
  • find_subnets_by_capability — Find subnets that provide a specific capability or service.
  • find_subnet_for_task — Identify the best subnet for a given task or use case.
  • get_subnet_health — Check the current health status of a subnet and its endpoints.
  • get_self_health — Retrieve the health status of the Metagraphed service itself.
  • list_endpoints — List all available endpoints for a subnet.
  • get_best_rpc_endpoint — Get the best-performing RPC endpoint for a subnet.
  • list_subnet_apis — List all public APIs published by a subnet.
  • get_api_schema — Retrieve the OpenAPI or other schema for a subnet's API.
  • how_do_i_call — Get guidance on how to call a subnet's API with examples.
  • verify_integration — Verify that an integration with a subnet is working correctly.
  • get_subnet_economics — Retrieve economic data: emission, alpha, yield for a subnet.
  • get_subnet_trajectory — Analyze how a subnet's economics are trending over time.
  • get_subnet_yield — Get yield information for a subnet.
  • compare_subnets — Compare economic and operational metrics across multiple subnets.
  • get_block — Retrieve chain block data directly from the Bittensor chain.
  • list_extrinsics — List extrinsics (transactions) on the Bittensor chain.
  • get_subnet_metagraph — Get the metagraph (validator/miner structure) for a subnet.
  • get_neuron — Retrieve detailed information about a specific neuron.
  • get_account — Get account information and portfolio data for a wallet.

Use cases

  • Discover which Bittensor subnets have public APIs available and check their current health status.
  • Integrate with a subnet's API by retrieving its OpenAPI schema and learning how to call it.
  • Analyze subnet economics, emission rates, and yield to compare investment opportunities.
  • Trace a wallet's activity and portfolio across all Bittensor subnets.
  • Query raw chain state, blocks, and extrinsics directly from the Bittensor blockchain.

metagraphed — Bittensor subnet operational registry MCP server FAQ

What is Metagraphed?

Metagraphed is an open registry and block explorer for Bittensor that provides machine-readable data on all 128 subnets, their APIs, health status, and schemas. It's not an official OpenTensor project but a community-built integration layer for developers and AI agents.

Is Metagraphed free to use?

Yes, Metagraphed is free and open-source (AGPL-3.0). The API is public and read-only, with no authentication required.

How do I use Metagraphed with Claude or Cursor?

Add the MCP server with URL `https://api.metagraph.sh/mcp` and transport `streamable-http`. For Claude CLI: `claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp`. For Cursor or other clients, add it to your MCP configuration with the same URL.

What data does Metagraphed provide?

Metagraphed provides subnet discovery, endpoint health (probe-derived every 15 minutes), API schemas, economics (emission, yield, alpha), chain state, wallet activity, and metagraph structure. All health data is probe-derived, not self-reported.

Do I need an API key or authentication?

No. Metagraphed is read-only and public. No API key, account, or authentication is required.

What are the different ways to access Metagraphed?

You can access it via MCP tools (for AI agents), REST API, GraphQL, typed clients (npm or PyPI), or the web UI at metagraph.sh.

README (reference)

Source of truth, from the repository.

<div align="center">

<a href="https://metagraph.sh"><img src="https://raw.githubusercontent.com/JSONbored/metagraphed/main/public/brand/banner-readme-mint.png" alt="Metagraphed — Bittensor subnet operational layer · data hub · API" width="820"></a>

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, 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 MCP MCP Registry mcp.so smithery badge npm PyPI License: AGPL-3.0

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

</div>

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

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

Add an MCP server with url https://api.metagraph.sh/mcp and transport streamable-http. No API key, no account, read-only.

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

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

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

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

🔮 GraphQL

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.

curl -X POST https://api.metagraph.sh/api/v1/graphql \
  -H 'content-type: application/json' \
  -d '{"query":"{ subnet(netuid: 7) { name health { status } surfaces { kind url } economics { emission_share } } }"}'

For agents

ResourceURL
Copyable agent prompt/agent.md
Agent workflows/agent-workflows.md
Machine index/llms.txt
GraphQL/api/v1/graphql — POST a shaped query (subnet + health + surfaces + endpoints + economics, provider + subnets, opportunity boards); GET returns the SDL
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

<!-- BEGIN:REGISTRY-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

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

<!-- END:REGISTRY-CATALOG -->

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

Related MCP servers

Search 1,300+ curated Claude agents, MCP servers, skills, and tools directly from your AI client.

273
MDX
MIT
View repository →

Connect After Effects to AI clients via local MCP endpoint with ExtendScript and native AEGP execution.

75
JavaScript
MIT
View repository →

Professional MCP server for video editing automation with OpenCut.

4
TypeScript
MIT
View repository →
MOMoxie Docs logo

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

2
TypeScript
MIT
View repository →

Cloud, GPU and LLM token prices with index fixings. Pay per call over x402 or with a prepaid key.

0
JavaScript
MIT
View repository →

Polish company registers: KRS extracts, Biała Lista VAT and bank account checks, ID validation.

0
C#
MIT
View repository →