MCP serverio.github.tytutueh13-sudo/woo-revenue-incident-graph
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
Overview
Score?
UNRATED 0.638
of what a free look can see, on 24 looks
Looks
30
last 11 hr ago
Tools
4
More info
URL
revenue-graph.utilityhouse.xyz/mcp/registry
streamable-http
Says it is
woo-revenue-incident-graph 0.2.0
protocol 2025-06-18
In the record since
28 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.638 · highest on record 0.8561
Toolsfrom sha256:24317b974e…0eee23
| Tool | Schema |
|---|---|
| check_checkout_change_risk 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? Chec |
input · output |
| diagnose_revenue_incident 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 priv |
input · output |
| get_checkout_health_snapshot 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 |
input · output |
| verify_revenue_recovery 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 |
input · output |
Verify it yourself
npx teppi-check https://revenue-graph.utilityhouse.xyz/mcp/registrycurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1TM9DEG2SEXTNKXSS8MQ47Y