Statusward Watches the Status of MCP Servers

Field notes

The monitoring sequence follows the connection steps a real MCP client would use: initialize, acknowledge initialization, then request the tool list. Statusward stores canonicalized tool-contract digests and places timestamped, tool-level differences in a changelog when they drift. The public board reports 42 probes across 14 servers, including GitHub, Stripe, Notion, and Cloudflare Docs. Unclaimed servers receive minimal reachability checks, while publishers can claim, tune, or opt out of monitoring.