Hosted vs self-run MCP: Watches & Alerts

This page compares a hosting model, not a tool-for-tool match: WingMan's own hosted Watches & Alerts tools (called over one shared MCP endpoint, metered per call) against third-party MCP servers in the same category that you install and run yourself. No server here is claimed to be equivalent to a specific WingMan tool - the comparison is setup and hosting model, drawn straight from each side's registry entry.

Tool	Price	Category
Cancel Watch	Metered - see /pricing	watches
Create Watch	Metered - see /pricing	watches
List Watches	Metered - see /pricing	watches

Server	Transport	What running it means	Install method
AnomalyArmor	`http`	Runs on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.	Remote endpoint (mcp-remote bridge for older clients)
com.ffmpeg-micro/mcp-server	`http`	Runs on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.	Remote endpoint (mcp-remote bridge for older clients)
com.googleapis.monitoring/mcp	`http`	Runs on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.	Remote endpoint (mcp-remote bridge for older clients)
New Relic MCP Server	`http`	Runs on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.	Remote endpoint (mcp-remote bridge for older clients)
Rootly	`sse`	Runs on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.	Remote endpoint (mcp-remote bridge for older clients)

Hosted vs self-run: Watches & Alerts

WingMan hosted

Self-run (third-party)

When to choose which

Choose the WingMan hosted tool(s) when

Choose a self-run server when