Woo Revenue Incident Graph
io.github.tytutueh13-sudo/woo-revenue-incident-graph · v0.2.2
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
MCPremoteno credentialsE-commerceFinanceKnowledge & docs
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 4 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 90/100
What it does: 4 tools · 4 read, 0 write · E-commerce, Finance, CRM & sales
Test call get_checkout_health_snapshot: worked (2,097 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +2
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +8
- Read/write annotations: +5
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://revenue-graph.utilityhouse.xyz/mcp/registryTools
4 tools listed at last check
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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.tytutueh13-sudo/woo-revenue-incident-graph)