subnet-37-status — metagraphed — Bittensor subnet operational registry MCP Resource
subnet-37-status
is one of 100 resources on the
metagraphed — Bittensor subnet operational registry
MCP server. Connect the server and your client can attach it as context.
by client
How to attach subnet-37-status from your client
- Claude Code metagraphed — Bittensor subnet operational registry Resource/subnet-37-status run in your project directory
- Claude Desktop metagraphed — Bittensor subnet operational registry Resource/subnet-37-status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor metagraphed — Bittensor subnet operational registry Resource/subnet-37-status ~/.cursor/mcp.json
- VS Code metagraphed — Bittensor subnet operational registry Resource/subnet-37-status .vscode/mcp.json
- Zed metagraphed — Bittensor subnet operational registry Resource/subnet-37-status ~/.config/zed/settings.json
- Windsurf metagraphed — Bittensor subnet operational registry Resource/subnet-37-status ~/.codeium/windsurf/mcp_config.json
- Cline metagraphed — Bittensor subnet operational registry Resource/subnet-37-status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI metagraphed — Bittensor subnet operational registry Resource/subnet-37-status ~/.gemini/settings.json
- Grok metagraphed — Bittensor subnet operational registry Resource/subnet-37-status .mcp.json (in your project root)
- ChatGPT metagraphed — Bittensor subnet operational registry Resource/subnet-37-status Settings → Connectors → Advanced → Developer mode
- Claude.ai metagraphed — Bittensor subnet operational registry Resource/subnet-37-status Settings → Connectors → Add custom connector
- LangChain metagraphed — Bittensor subnet operational registry Resource/subnet-37-status pip install langchain-mcp-adapters
Other resources on this server
- registry-summary
- agent-catalog
- coverage-depth
- schema-index
- chain-stream
- subnet-0
- subnet-0-status
- subnet-1
- subnet-1-status
- subnet-2
- subnet-2-status
- subnet-3
- subnet-3-status
- subnet-4
- subnet-4-status
- subnet-5
- subnet-5-status
- subnet-6
- subnet-6-status
- subnet-7
- subnet-7-status
- subnet-8
- subnet-8-status
- subnet-9
- subnet-9-status
- subnet-10
- subnet-10-status
- subnet-11
- subnet-11-status
- subnet-12
- subnet-12-status
- subnet-13
- subnet-13-status
- subnet-14
- subnet-14-status
- subnet-15
- subnet-15-status
- subnet-16
- subnet-16-status
- subnet-17
metagraphed — Bittensor subnet operational registry also offers 6 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.