Metagraphed Bittensor Subnet Registry
Metagraphed — Bittensor Subnet Registry (MCP)
The public-interface registry for Bittensor subnets, exposed as MCP tools. Point any MCP-aware client at the hosted endpoint and query 100+ subnets' live APIs, JSON schemas, RPC endpoints, on-chain economics, and probe-derived health — no API key required.
Hosted · remote · no auth → https://api.metagraph.sh/mcp (streamable-http)
Connect
Claude Code: ``` claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp ```
Claude Desktop / Cursor / other clients: ```json { "mcpServers": { "metagraphed": { "type": "streamable-http", "url": "https://api.metagraph.sh/mcp" } } } ```
(stdio-only clients can bridge with npx -y mcp-remote https://api.metagraph.sh/mcp.)
Tools
Discover — search_subnets, list_subnets, find_subnets_by_capability, semantic_search, find_subnet_for_task, ask, find_subnet_opportunities, list_enrichment_targets, registry_summary
Inspect a subnet — get_subnet, get_subnet_health, get_subnet_economics, get_subnet_trajectory, get_subnet_metagraph, list_subnet_validators, get_neuron
Integrate — list_subnet_apis, get_api_schema, get_fixture, get_best_rpc_endpoint, how_do_i_call, verify_integration, get_agent_catalog
Why
Most Bittensor subnets publish an API, docs, or RPC somewhere — but there's no single machine-readable index. Metagraphed crawls, verifies, and probes them, then serves a clean registry with probe-derived health (never hand-set), JSON-schema contracts, and freshness. The MCP server makes all of it directly callable by agents.
Links
- Website: https://metagraph.sh
- REST API + OpenAPI: https://api.metagraph.sh
- Agent docs: https://api.metagraph.sh/llms.txt
- Source: https://github.com/JSONbored/metagraphed
Server Config
{
"mcpServers": {
"metagraphed": {
"type": "streamable-http",
"url": "https://api.metagraph.sh/mcp"
}
}
}