# `io.github.tytutueh13-sudo/woo-revenue-incident-graph` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/io.github.tytutueh13-sudo/woo-revenue-incident-graph
- JSON: https://radar.anlyon.com/api/v1/servers/io.github.tytutueh13-sudo/woo-revenue-incident-graph
- Version: 0.2.2 (active)
- Publisher: io.github.tytutueh13-sudo (GitHub account)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-21T18:51:04.615Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Woo Revenue Incident Graph
Check WooCommerce checkout-change risk using public evidence and privacy-safe store signals.
```

Scanned 2026-11-21T10:17:54.784Z over streamable-http.

**4 tools: 3 change things and 1 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 3 | ask |
| Only reads | read | 1 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged private-data or outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | `mcp__woo-revenue-incident-graph__check_checkout_change_risk` `mcp__woo-revenue-incident-graph__diagnose_revenue_incident` `mcp__woo-revenue-incident-graph__get_checkout_health_snapshot` `mcp__woo-revenue-incident-graph__verify_revenue_recovery` |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **warn** Annotations that disagree with the tool in `check_checkout_change_risk` ([annotation-conflict](https://radar.anlyon.com/methodology#annotation-conflict))

```untrusted-server-text
The server marks "check_checkout_change_risk" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "check_checkout_change_risk" says "checkout": a word for a change.
```


## Changes things (3)

Creates or changes something that can be changed back. Claude Code: ask.

### `check_checkout_change_risk`

- The name "check_checkout_change_risk" says "checkout": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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_incident`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data.

Description, as the server wrote it:

```untrusted-server-text
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.
```

### `verify_revenue_recovery`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data.

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Only reads (1)

Looks things up and changes nothing. Claude Code: allow.

### `get_checkout_health_snapshot`

- The name "get_checkout_health_snapshot" says "get": a word for reading.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data.

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `woo-revenue-incident-graph`:

```json
{
  "permissions": {
    "allow": [
      "mcp__woo-revenue-incident-graph__get_checkout_health_snapshot"
    ],
    "ask": [
      "mcp__woo-revenue-incident-graph__diagnose_revenue_incident",
      "mcp__woo-revenue-incident-graph__check_checkout_change_risk",
      "mcp__woo-revenue-incident-graph__verify_revenue_recovery"
    ],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__woo-revenue-incident-graph__get_checkout_health_snapshot`: untrusted-input
- `mcp__woo-revenue-incident-graph__diagnose_revenue_incident`: untrusted-input
- `mcp__woo-revenue-incident-graph__check_checkout_change_risk`: untrusted-input
- `mcp__woo-revenue-incident-graph__verify_revenue_recovery`: untrusted-input

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-20T19:12:23.307Z, unchanged since 2026-10-22T15:06:59.467Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| Reachable | `yes` |
| HTTP status of an anonymous initialize | `200` |
| tools/list served without credentials | `yes` |
| Tools that change things, listed without credentials | `3` |
| Protocol version | `2025-06-18` |
| WWW-Authenticate on 401 | `not observed` |
| resource_metadata in WWW-Authenticate | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://radar.anlyon.com/methodology#unauth-remote-writes))

```untrusted-server-text
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

https://revenue-graph.utilityhouse.xyz/mcp/registry: tools/list returned 4 tools to an anonymous client, including diagnose_revenue_incident (write), check_checkout_change_risk (write), verify_revenue_recovery (write)
```
