monitor_timeseries — WaveGuard MCP Prompt

monitor_timeseries is one of 6 prompts on the WaveGuard MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke monitor_timeseries from your client

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

Other prompts on this server

• detect_anomalies
• spreadsheet_quality_check
• token_risk_assessment
• wallet_behavior_check
• volume_authenticity_check

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.