# io.github.lazytitan30/billing-doctor (npm · billing-doctor)

Diagnose Google Play Billing incidents locally, with evidence. Not affiliated with Google.

- Trust score: 86/100 (high trust)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `billing-doctor`: 86/100 (this document), [markdown](https://verifymcp.io/servers/lazytitan30-billing-doctor/billing-doctor.md), [page](https://verifymcp.io/servers/lazytitan30-billing-doctor/billing-doctor)

## Channel facts

- Registry: `npm`
- Package: `billing-doctor`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 4 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to lazytitan30/billing-doctor).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 618 tokens (~103/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.lazytitan30/billing-doctor MCP server?

io.github.lazytitan30/billing-doctor runs locally as an npm package, launched with npx -y billing-doctor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lazytitan30-billing-doctor -- npx -y billing-doctor
```

### Cursor

```json
{
  "mcpServers": {
    "lazytitan30-billing-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "billing-doctor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lazytitan30-billing-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "billing-doctor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lazytitan30-billing-doctor -- npx -y billing-doctor
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lazytitan30-billing-doctor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "billing-doctor"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lazytitan30-billing-doctor --command npx --arg -y --arg billing-doctor
```

### Hermes

```yaml
mcp_servers:
  lazytitan30-billing-doctor:
    command: "npx"
    args: ["-y", "billing-doctor"]
```

### Netclaw

```json
{
  "McpServers": {
    "lazytitan30-billing-doctor": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "billing-doctor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lazytitan30-billing-doctor -t stdio -c npx -a -y billing-doctor
```

### Other

```json
{
  "mcpServers": {
    "lazytitan30-billing-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "billing-doctor"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 84, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-16 (score 69, −3)

- [security regression] Malware scan: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: lazytitan30/billing-doctor
- [functional improvement] Stability: unverified → 0.10
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-09-14 (score 72, +16)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Security disclosure: unverified → pass

### 2026-09-13 (score 56)

First indexed and scored.

## MCP tools (6)

### `diagnose_timeline` (~106 tokens)

Diagnose a purchase timeline

Run every rule over a billing-doctor-timeline/1 document and return the findings, sorted by severity then first evidence index. Each finding has ruleId, severity, title, evidence (event indexes), mechanism, googleRule {quote, url, readOn}, confidence, nextCheck and fix. exitCode is 1 when a high finding exists.

Input parameters:

- `rules` (array): Run only these rule ids
- `timeline` (required): The timeline as an object or as JSON text

### `explain_subscription_state` (~123 tokens)

Explain a subscription resource

Explain a purchases.subscriptionsv2 resource in plain words: the state, the access it implies under Google's rule and under the given policy, the expiry per line item, the acknowledgement deadline, the linked token, the test marker, the plan type and the cancellation context.

Input parameters:

- `grantOn` (array): States the backend grants access on
- `now` (string): ISO time to evaluate deadlines at; default now
- `resource` (required): The SubscriptionPurchaseV2 as an object or JSON text
- `revokeOn` (array): States the backend revokes on

### `decode_rtdn` (~83 tokens)

Decode a real-time developer notification

Decode a Pub/Sub push body (or a decoded DeveloperNotification, or the base64 data alone): the notification kind, the type name for the integer, the token, and the next step, which for a subscription notification is always to re-fetch the resource before touching state.

Input parameters:

- `message` (required): The push envelope, the notification object, or the base64 data

### `redact_text` (~79 tokens)

Redact a log

Replace purchase tokens with stable tok_ pseudonyms, remove emails, mask order ids to their last four characters, turn UUIDs into u_ pseudonyms and cut out private keys and bearer tokens. Run it over logs before building a timeline.

Input parameters:

- `salt` (string): Mixed into the pseudonyms
- `text` (string, required): The text to redact

### `list_rules` (~23 tokens)

List the rule catalogue

Every rule: id, group, severity, title and what it detects.

### `get_rule` (~66 tokens)

Get one rule

One rule in full: what it detects, Google's rule quoted with the URL and the date it was read, the observed behaviour when there is one, and the runbook entry when the Incident Kit folder is present.

Input parameters:

- `id` (string, required): The rule id, for example B1

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/lazytitan30-billing-doctor/billing-doctor#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 85
- 2026-09-18: 85
- 2026-09-17: 84
- 2026-09-16: 69
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 56

## Common questions

### What is the io.github.lazytitan30/billing-doctor MCP server?

io.github.lazytitan30/billing-doctor is an MCP server listed in the public MCP registry as io.github.lazytitan30/billing-doctor. Diagnose Google Play Billing incidents locally, with evidence. Not affiliated with Google. This page covers its npm package (billing-doctor).

### Is the io.github.lazytitan30/billing-doctor MCP server safe to use?

io.github.lazytitan30/billing-doctor scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.lazytitan30/billing-doctor MCP server expose?

io.github.lazytitan30/billing-doctor exposes 6 tools: diagnose_timeline, explain_subscription_state, decode_rtdn, redact_text, list_rules, get_rule. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.

### Is the io.github.lazytitan30/billing-doctor MCP server still maintained?

io.github.lazytitan30/billing-doctor is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.lazytitan30/billing-doctor MCP server under?

io.github.lazytitan30/billing-doctor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/billing-doctor
- Socket report: https://socket.dev/npm/package/billing-doctor
- Repository: https://github.com/lazytitan30/billing-doctor
- Changelog RSS feed: https://verifymcp.io/servers/lazytitan30-billing-doctor/billing-doctor.xml
- Changelog JSON feed: https://verifymcp.io/servers/lazytitan30-billing-doctor/billing-doctor.json
- HTML version of this page: https://verifymcp.io/servers/lazytitan30-billing-doctor/billing-doctor