Woo Revenue Incident Graph
io.github.tytutueh13-sudo/woo-revenue-incident-graphCheck WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
Score: 100/100
Handshake verified by our own probe.
Tools · 4
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 cha…
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 — o…
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 v…
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 f…
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://revenue-graph.utilityhouse.xyz/mcp/registry
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"woo_revenue_incident_graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry",
"transport": "streamable-http"
}
}
}