Woo Revenue Incident Graph is an MCP server with 4 tools an agent can call, among them check_checkout_change_risk, diagnose_revenue_incident, get_checkout_health_snapshot. It answers at https://revenue-graph.utilityhouse.xyz/mcp/registry over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 Inputs: component, to_version |
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 tran Inputs: symptom, window_seconds |
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/s Inputs: window_seconds |
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. Inputs: change_applied_at, window_seconds |
Every block below points at https://revenue-graph.utilityhouse.xyz/mcp/registry. Pick your client and copy.
claude mcp add --transport http woo-revenue-incident-graph https://revenue-graph.utilityhouse.xyz/mcp/registry
{
"mcpServers": {
"woo-revenue-incident-graph": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://revenue-graph.utilityhouse.xyz/mcp/registry"]
}
}
}{
"mcpServers": {
"woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}{
"servers": {
"woo-revenue-incident-graph": {
"type": "http",
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}{
"context_servers": {
"woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"woo-revenue-incident-graph": {
"serverUrl": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}name: Woo Revenue Incident Graph
version: 0.0.1
schema: v1
mcpServers:
- name: Woo Revenue Incident Graph
type: streamable-http
url: https://revenue-graph.utilityhouse.xyz/mcp/registry{
"mcpServers": {
"woo-revenue-incident-graph": {
"httpUrl": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"woo-revenue-incident-graph": {
"type": "http",
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"woo-revenue-incident-graph": {
"url": "https://revenue-graph.utilityhouse.xyz/mcp/registry"
}
}
}goose://extension?url=https%3A%2F%2Frevenue-graph.utilityhouse.xyz%2Fmcp%2Fregistry&type=streamable_http&id=woo-revenue-incident-graph&name=Woo%20Revenue%20Incident%20Graph
It answered our last check on 24 October 2026 in 1449 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
4, as returned by the server's own tools/list on 22 September 2026: check_checkout_change_risk, diagnose_revenue_incident, get_checkout_health_snapshot, verify_revenue_recovery.
It answered our last check on 24 October 2026 in 1449 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://revenue-graph.utilityhouse.xyz/mcp/registry. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.tytutueh13-sudo. Endpoint host: revenue-graph.utilityhouse.xyz. ARD identifier: urn:air:io.github.tytutueh13-sudo:mcp:woo-revenue-incident-graph.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.