NestDaddy

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.

Connect Remote server

Terminal
claude mcp add --transport http woo-revenue-incident-graph https://revenue-graph.utilityhouse.xyz/mcp/registry
~/.cursor/mcp.json
{
  "mcpServers": {
    "woo-revenue-incident-graph": {
      "url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "woo-revenue-incident-graph": {
      "type": "http",
      "url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://revenue-graph.utilityhouse.xyz/mcp/registry

Tools 4 found in our last check

  • 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 status with the change across the window, gateway/webhook/scheduler health, checkout page health,…

  • 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 privacy-safe signals — order status over time, order-status transitions, order-note reason codes, gatew…

  • 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? Checks a component and version against public release and issue evidence scoped to the money path (paym…

  • 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 order mix, webhook failure counts, and gateway availability. Returns `resolved`, `improving`, `stil…

Details

Endpointhttps://revenue-graph.utilityhouse.xyz/mcp/registry (Streamable HTTP)
First published5 Sep 2026
Last updated5 Sep 2026
Registry nameio.github.tytutueh13-sudo/woo-revenue-incident-graph

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.