Metagraphed — Bittensor Subnet Operational Registry MCP Server

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

Local serverstdioPython

What is the Metagraphed — Bittensor Subnet Operational Registry MCP server?

Most developer tooling work still happens through a UI a human drives. Metagraphed — Bittensor Subnet Operational Registry MCP server moves it into the conversation instead. Live operational + integration registry for Bittensor subnets: APIs, schemas, health.

The short version

Bittensor didn't ship with a map, so we drew one. For every subnet: what does it expose (public APIs, docs, schemas), is it healthy, and how do I call it — machine-readable and agent-native from the ground up.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • Schema — first edits** require npm run build (regenerates openapi.json + types)
  • Resource — URL
  • GraphQL/api/v1/graphql — POST a shaped query (subnet + health + surfaces + endpoints + economics, provider +

Getting it running

Installation goes through your MCP client rather than a global install: point it at @jsonbored/metagraphed on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Metagraphed — Bittensor Subnet Operational Registry's toolset — Schema, Resource, GraphQL — is a fair guide to whether it matches your workflow. It is maintained by JSONbored; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Metagraphed — Bittensor Subnet Operational Registry's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Schemafirst edits** require npm run build (regenerates openapi.json + types).
ResourceURL
GraphQL[/api/v1/graphql](https://api.metagraph.sh/api/v1/graphql) — POST a shaped query (subnet + health + surfaces + endpoints + economics, provider + subnets, opportunity boards); GET returns the SDL

How to install the Metagraphed — Bittensor Subnet Operational Registry MCP server

{
  "mcpServers": {
    "metagraphed": {
      "command": "npx",
      "args": ["-y", "@jsonbored/metagraphed"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Metagraphed — Bittensor Subnet Operational Registry to Schema.
  • Use Metagraphed — Bittensor Subnet Operational Registry to Resource.
  • Use Metagraphed — Bittensor Subnet Operational Registry to GraphQL.

Frequently asked questions

It connects Metagraphed — Bittensor Subnet Operational Registry to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Schema, Resource, GraphQL) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Metagraphed — Bittensor Subnet Operational Registry directly.