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 分