INDIVIDUAL MCP TOOL
get_account_serving
Fetch one account's AxonServed axon-endpoint serving footprint per subnet over the requested window (7d, 30d, or 90d; default 30d): each subnet's announcement count with the first and last AxonServed timestamps, plus account totals, an HHI concentration of where its serving activity is focused, and the dominant subnet.
LIVE ENDPOINT
https://api.metagraph.sh/mcp
Connect to this endpoint to inspect the live schema for get_account_serving and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests retrieving external content.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.metagraphed]
url = "https://api.metagraph.sh/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"metagraphed": {
"type": "http",
"url": "https://api.metagraph.sh/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: metagraphed
Remote MCP URL: https://api.metagraph.sh/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"metagraphed": {
"url": "https://api.metagraph.sh/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"metagraphed": {
"type": "http",
"url": "https://api.metagraph.sh/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "metagraphed",
"transport": "streamable-http",
"url": "https://api.metagraph.sh/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_more_tools— Call this ONLY when you have looked through the available tools and none of them can do what you need.search_subnets— Full-text search across Bittensor subnets by name, slug, capability, or keyword.list_subnets— Enumerate the full Bittensor subnet registry, paginated.find_subnets_by_capability— Find Bittensor subnets that expose callable services (APIs, OpenAPI schemas, SSE streams) matching a capability or category.get_subnet— Fetch the composed overview for one subnet by netuid: identity, completeness, curated surfaces, health summary, gaps, and counts.get_subnet_detail— Fetch one subnet's raw per-subnet record by netuid: chain-native structure, live economics, candidate surfaces, endpoints, gaps, and verified surfaces -- the underlying record get_subnet's composed overview is assembled from.get_subnet_snapshot— Fan out to five of a subnet's live views in a single round trip: hyperparameters, stake/emission concentration, reward-distribution performance, the top validators by stake (default 10, cap with top_validators_limit), and the most recent chain events (default 10, cap with recent_events_limit).get_network_health— Fetch the live global operational health rollup: global surface counts by status (ok/degraded/failed/unknown) and per-subnet operational status from the ~15-minute health prober (KV health:current → Postgres surface_status).