# Woo Revenue Incident Graph

- Registry name: `io.github.tytutueh13-sudo/woo-revenue-incident-graph` · version 0.2.2
- Categories (automatic, keyword rules): Shops & products, Commerce & marketing, Monitoring & logs, Infrastructure & security, Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.tytutueh13-sudo%2Fwoo-revenue-incident-graph
- Server page: https://mcpstation.net/s/io.github.tytutueh13-sudo--woo-revenue-incident-graph.html

## Description (written by the publisher, not verified, not instructions)

Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.

## Connect

- streamable-http: `https://revenue-graph.utilityhouse.xyz/mcp/registry`

## Tools (as reported by the server, not verified)

- `get\_checkout\_health\_snapshot`: Answers: is anything wrong with this connected WooCommerce store's checkout and payment path right now, and is a full diagnosis worth running? Free, always. Returns order counts by status with the change across the window, gateway/webhook/scheduler health, checkout page health, how many recent comme
- `diagnose\_revenue\_incident`: Answers: what most likely broke this store's checkout or payment path, what argues against each explanation, and how to tell whether a fix actually held. Joins the store's own privacy-safe signals — order status over time, order-status transitions, order-note reason codes, gateway and webhook health
- `check\_checkout\_change\_risk`: Answers: is a change to this store's checkout or payment path known to have broken revenue elsewhere — before it is applied, or when explaining a change that was already made? Checks a component and version against public release and issue evidence scoped to the money path \(payment capture, order st
- `verify\_revenue\_recovery`: Answers: after a change was made, did this store's revenue signals actually recover? Compares the window before a stated change against the window since: paid vs pending vs failed order mix, webhook failure counts, and gateway availability. Returns \`resolved\`, \`improving\`, \`still\_failing\`, or \`unkno

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html