metagraphed — Bittensor subnet operational registry

io.github.JSONbored由 GitHub 账号 JSONbored 发布v1.3.0更新于 Oct 25, 2026

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

已验证Streamable HTTP可网页运行金融开发者工具数据与分析

概览

AI 生成的概览

一个需账户认证的远程 MCP 服务器，基于 Metagraphed 注册表，让助手查询 Bittensor 子网、端点健康、经济数据与链上状态。

可以做什么
按关键词、语义、能力或任务匹配发现子网，并基于注册表提出带引用的问答。检查子网与端点健康状态，列出端点并选出最佳 RPC 端点。查询各子网公开的 API 与 schema，获取调用说明并验证集成。读取子网经济数据、走势、收益率并比较不同子网。读取区块、外部交易、元图和神经元等链上状态，并追踪账户事件、所属子网与持仓。
适用场景
适合在开发或排查 Bittensor 子网集成时使用，让助手找到合适的子网、确认端点是否在线并了解应发送什么请求。也适合在对话中直接查看子网经济数据、链上状态和钱包活动。
运行要求
远程 Streamable-HTTP 端点 api.metagraph.sh，无需本地安装包。需要 OAuth 登录（免费账户），或不支持 OAuth 的客户端使用签发的 API key，通过 Authorization Bearer 请求头发送。需要能访问该服务的网络。
安装前请注意
必须进行账户认证，凭据缺失或无效会返回 401。README 称服务为只读且非托管，质押与委托在客户端签名、密钥不会传到后端，但这只是提供方说法。查询与账户查询会发送给第三方服务，健康数据来自探测而非自报。

安装

在 SourceWeft 中

  1. 打开 控制台中的 metagraphed — Bittensor subnet operational registry，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.JSONbored%2Fmetagraphed/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

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

README

[Metagraphed — Bittensor subnet operational layer · data hub · API]

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.

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

json
{  "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.

bash
npm i @jsonbored/metagraphed   # JS/TSpip install metagraphed        # Python
🌐 REST

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

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

text
docs/              product + operating notes (start here)registry/          subnet overlays, candidates, community submissionsschemas/           canonical JSON Schema componentsscripts/           validation, generation, probe, safetyworkers/           Cloudflare Worker API routespublic/metagraph/  compact generated artifacts + contractsgenerated/         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

来源：README.md，提交 bcd6fd5

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.3.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分