Woo Revenue Incident Graph
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
Connect it
Settings → Connectors → Add custom connector
URL: https://revenue-graph.utilityhouse.xyz/mcp/registrySettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://revenue-graph.utilityhouse.xyz/mcp/registry{
"mcpServers": {
"woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}claude mcp add --transport http woo-revenue-incident-graph https://revenue-graph.utilityhouse.xyz/mcp/registry{
"servers": {
"woo-revenue-incident-graph": {
"type": "http",
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}4 tools, verified live
get_checkout_health_snapshotread-onlyAnswers: 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 commerce changes there were, which signal families this store can and cannot report, and how fresh the un
diagnose_revenue_incidentread-onlyAnswers: 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, scheduler backlog, checkout page health, recent plugin/theme/core changes — against public release
check_checkout_change_riskread-onlyAnswers: 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 status transitions, gateway webhooks, wallet checkout), not to general plugin update safety. With no c
verify_revenue_recoveryread-onlyAnswers: 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 `unknown` — and `unknown` when too little new data has arrived to tell, which is free. A quiet ten minutes
Alternatives in Developer Tools
Compare →ZTZoom TasksOfficialA
Zoom Tasks server for creating, updating, assigning, and synchronizing task workflows.
ZDZoom DocsOfficialA
Zoom Docs server for creating and retrieving Zoom documents and notes in Markdown.
ZWZoom WhiteboardOfficialA
Zoom Whiteboard server for creating boards and diagrams and locating existing boards.
ZWZoom WorkspaceOfficialA
Zoom workspace server for meetings, chat, docs, recordings, and AI-generated collaboration content.
KeployA
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
ShipStaticA
Deploy static websites, landing pages, and prototypes instantly from AI agents.