network_health_report — Parallax Protocol MCP Prompt
network_health_report
is one of 3 prompts on the
Parallax Protocol
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke network_health_report from your client
- Claude Code Parallax Protocol Prompt/network_health_report run in your project directory
- Claude Desktop Parallax Protocol Prompt/network_health_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Parallax Protocol Prompt/network_health_report ~/.cursor/mcp.json
- VS Code Parallax Protocol Prompt/network_health_report .vscode/mcp.json
- Zed Parallax Protocol Prompt/network_health_report ~/.config/zed/settings.json
- Windsurf Parallax Protocol Prompt/network_health_report ~/.codeium/windsurf/mcp_config.json
- Cline Parallax Protocol Prompt/network_health_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Parallax Protocol Prompt/network_health_report ~/.gemini/settings.json
- Grok Parallax Protocol Prompt/network_health_report .mcp.json (in your project root)
- ChatGPT Parallax Protocol Prompt/network_health_report Settings → Connectors → Advanced → Developer mode
- Claude.ai Parallax Protocol Prompt/network_health_report Settings → Connectors → Add custom connector
- LangChain Parallax Protocol Prompt/network_health_report pip install langchain-mcp-adapters
Other prompts on this server
Parallax Protocol also offers 11 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 13 October 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.