Metagraphed Bittensor Subnet Registry
About
The public-interface registry for Bittensor subnets, as MCP tools. Query 100+ subnets' live APIs, JSON schemas, RPC endpoints, on-chain economics, and probe-derived health — plus semantic search and natural-language Q&A. Hosted, remote, no API key.
Details
- Author
- JSONbored
- Downloads
- 432
- Categories
- Developer Tools, API
Jump to
- Search and discover subnets by capability or task
- Inspect live health, economics, and trajectory of any subnet
- List subnet APIs with machine-readable JSON schemas
- Get probe-derived health (never hand-set) and freshness
- Retrieve the best RPC endpoint for a subnet
- No API key required; fully hosted and remote
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Metagraphed Bittensor Subnet RegistryCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Add the hosted endpoint to your MCP client using the streamable-http transport with URL https://api.metagraph.sh/mcp. For Claude Code, run claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp. For Claude Desktop, Cursor, or other clients, add a JSON config. Stdio-only clients can bridge with npx -y mcp-remote https://api.metagraph.sh/mcp.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"metagraphed bittensor subnet registry": {
"metagraphed": {
"type": "streamable-http",
"url": "https://api.metagraph.sh/mcp"
}
}
}
}McpServers
{
"metagraphed": {
"type": "streamable-http",
"url": "https://api.metagraph.sh/mcp"
}
}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/metagraphedSign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
