monitor_my_validator — metagraphed — Bittensor subnet operational registry MCP Prompt

monitor_my_validator is one of 6 prompts on the metagraphed — Bittensor subnet operational registry MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke monitor_my_validator from your client

• Claude Code metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator run in your project directory
• Claude Desktop metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator ~/.cursor/mcp.json
• VS Code metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator .vscode/mcp.json
• Zed metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator ~/.config/zed/settings.json
• Windsurf metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator ~/.codeium/windsurf/mcp_config.json
• Cline metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator ~/.gemini/settings.json
• Grok metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator .mcp.json (in your project root)
• ChatGPT metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator Settings → Connectors → Advanced → Developer mode
• Claude.ai metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator Settings → Connectors → Add custom connector
• LangChain metagraphed — Bittensor subnet operational registry Prompt/monitor_my_validator pip install langchain-mcp-adapters

Other prompts on this server

• integrate_with_subnet
• find_subnet_for_task
• check_health_and_fallbacks
• evaluate_subnet_before_staking
• audit_account_history

metagraphed — Bittensor subnet operational registry also offers 100 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.