evaluate_signal — Uphealth Signal MCP Prompt

evaluate_signal is one of 2 prompts on the Uphealth Signal MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke evaluate_signal from your client

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

Other prompts on this server

• pick_template

Uphealth Signal also offers 2 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.