All servers · Shops & products · Monitoring & logs · Payments & accounting
Woo Revenue Incident Graph
io.github.tytutueh13-sudo/woo-revenue-incident-graph · v0.2.2
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
Connect
streamable-http · https://revenue-graph.utilityhouse.xyz/mcp/registry
claude mcp add --transport http woo-revenue-incident-graph https://revenue-graph.utilityhouse.xyz/mcp/registry{
"mcpServers": {
"woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}Tools as reported by the server
get_checkout_health_snapshotAnswers: 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 commediagnose_revenue_incidentAnswers: 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 healthcheck_checkout_change_riskAnswers: 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 stverify_revenue_recoveryAnswers: 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
JSON · Text for agents · Registry updated 2026-09-05