metagraphed — Claude Code MCP server for Bittensor subnets
An MCP server that maps Bittensor subnets: which APIs they expose, whether endpoints answer, and how to call them.
claude mcp add --transport http metagraphed https://api.metagraph.sh/mcpWhat metagraphed — Bittensor subnet operational registry does
Metagraphed keeps a registry of Bittensor subnets in one place: the public interfaces each one publishes, their schemas, endpoint status, and notes on how to call them. Health numbers come from its own probes rather than from what subnets report about themselves. The block explorer runs on a Rust indexer built in-house, so no third-party RPC sits in the path.
You connect it as a Streamable-HTTP MCP server at https://api.metagraph.sh/mcp. Sign-in is free but an account is required: the client walks through OAuth, and for automation you send an issued key as Authorization: Bearer <mg_api_key>. Requests without valid credentials get a 401 plus the sign-in metadata. Tools are grouped around discovery, health checks, integration, economics, chain state, wallets, and cited answers.
Short on chat context? Append ?search_page_size=1 or 2 to the URL. search_tools then returns fewer full definitions per page, and next_cursor leads to the rest. Individual schemas and tool results stay the same size. Staking and delegation are signed in the wallet on your side, so keys never reach the backend.
What it helps with
- find a subnet that exposes a public API for a task
- check whether a subnet endpoint is answering right now
- pull an API schema and a working call example
- compare subnet economics and see how they trend
- see what one wallet does across the network
Example prompts for the agent
- Which Bittensor subnets expose a public API I can call today?
- Show me the OpenAPI spec for SN64 and whether it's healthy
- What changed on subnet 38 over the past week?
How to install metagraphed — Bittensor subnet operational registry
Platform CLI: remote server
claude mcp add --transport http metagraphed https://api.metagraph.sh/mcpPlatform CLI: remote server
codex mcp add metagraphed-bittensor-subnet-operational-registry --url https://api.metagraph.sh/mcpConfig file
{
"mcpServers": {
"metagraphed-bittensor-subnet-operational-registry": {
"url": "https://api.metagraph.sh/mcp"
}
}
}Config file
{
"servers": {
"metagraphed-bittensor-subnet-operational-registry": {
"type": "http",
"url": "https://api.metagraph.sh/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http metagraphed-bittensor-subnet-operational-registry https://api.metagraph.sh/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about metagraphed — Bittensor subnet operational registry
How do I install metagraphed in Claude Code?
Run claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp. The client will then prompt you to complete OAuth sign-in.
What does metagraphed do?
It maintains a registry of Bittensor subnets — public APIs and schemas, endpoint health, economics, chain and wallet data — and exposes it to your agent as MCP tools.
Do I need an API key?
OAuth clients just sign in. For automation or clients without OAuth, an issued key goes in the Authorization: Bearer <mg_api_key> header.
