Woo Revenue Incident Graph MCP server

• check_checkout_change_riskFree

  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 status transitions, gateway webhooks, wallet checkout), not to general plugin update safety. With no component named, checks every commerce change this store has made recently. Says `unknown` when nothing independent is on record — an absence of reports is not a safety record, and is reported as the absence it is. Free.

• diagnose_revenue_incidentFree

  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, scheduler backlog, checkout page health, recent plugin/theme/core changes — against public release and issue evidence, on one timeline. Every answer reports which signal families this store could and could not report, because a family that cannot be collected is not a family that is fine. Returns up to three ranked hypotheses, each with the observations behind it, independent public sources where they exist, counterevidence, what remains unknown, safe next steps, and a verification plan. Returns `abstained` and charges nothing when the snapshot is stale, coverage is thin, or the signals do not support any cause — an unsupported guess during an outage is worse than no answer. Free while in beta. Call get_checkout_health_snapshot first.

• get_checkout_health_snapshotFree

  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 commerce changes there were, which signal families this store can and cannot report, and how fresh the underlying data is. Call this FIRST — it is cheap, and `diagnosis_recommended` tells you whether the expensive call would have anything to work with. It returns no customer, order, or payment identifier because the store never sends any.

• verify_revenue_recoveryFree

  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 `unknown` — and `unknown` when too little new data has arrived to tell, which is free. A quiet ten minutes is not a recovery. Free while in beta.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 4080ms17/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Woo Revenue Incident Graph: common questions

Is Woo Revenue Incident Graph MCP server safe?

With care: it is graded C, so read the findings first (63/100). Read the Woo Revenue Incident Graph safety report

How do I install Woo Revenue Incident Graph?

It runs remotely at revenue-graph.utilityhouse.xyz. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Woo Revenue Incident Graph need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Woo Revenue Incident Graph maintained?

The latest release is v0.2.2.

Is Woo Revenue Incident Graph up?

100% of our last 5 checks got an answer. We check remote servers about four times a day.

What can I use instead of Woo Revenue Incident Graph?

Servers from other publishers that do the same job: SCVD General Store MCP server, DebugBundle MCP server and knowmind MCP server. Compare all Woo Revenue Incident Graph alternatives.