io.github.lazytitan30/billing-doctor
NPM · BILLING-DOCTOR · SCANNED SEP 20
Diagnose Google Play Billing incidents locally, with evidence. Not affiliated with Google.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lazytitan30/billing-doctor). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 618 tokens (~103/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · billing-doctor
claude mcp add lazytitan30-billing-doctor -- npx -y billing-doctor
{
"mcpServers": {
"lazytitan30-billing-doctor": {
"command": "npx",
"args": [
"-y",
"billing-doctor"
]
}
}
} {
"servers": {
"lazytitan30-billing-doctor": {
"command": "npx",
"args": [
"-y",
"billing-doctor"
]
}
}
} codex mcp add lazytitan30-billing-doctor -- npx -y billing-doctor
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lazytitan30-billing-doctor": {
"type": "local",
"command": [
"npx",
"-y",
"billing-doctor"
],
"enabled": true
}
}
} openclaw mcp add lazytitan30-billing-doctor --command npx --arg -y --arg billing-doctor
mcp_servers:
lazytitan30-billing-doctor:
command: "npx"
args: ["-y", "billing-doctor"] {
"McpServers": {
"lazytitan30-billing-doctor": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"billing-doctor"
]
}
}
} assistant mcp add lazytitan30-billing-doctor -t stdio -c npx -a -y billing-doctor
{
"mcpServers": {
"lazytitan30-billing-doctor": {
"command": "npx",
"args": [
"-y",
"billing-doctor"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Sept 26 −3
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: lazytitan30/billing-doctor security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 14 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → pass ▲ functional
- 13 Sept 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/billing-doctor@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | lazytitan30/billing-doctor |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/lazytitan30/billing-doctor/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 2856010314 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7a06c30bbe8549b53eb0f5fa695d9284d9ee60d9e642228dc480b64e4cedea34a90a7b190d0aff87255b574139737d817a5d1d5861a6cbcddc5be0e52 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
decode_rtdn Decode a real-time developer notification ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | – | yes | The push envelope, the notification object, or the base64 data |
No output schema declared.
No examples provided.
diagnose_timeline Diagnose a purchase timeline ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | – | Run only these rule ids |
| timeline | – | yes | The timeline as an object or as JSON text |
No output schema declared.
No examples provided.
explain_subscription_state Explain a subscription resource ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| grantOn | array | – | States the backend grants access on |
| now | string | – | ISO time to evaluate deadlines at; default now |
| resource | – | yes | The SubscriptionPurchaseV2 as an object or JSON text |
| revokeOn | array | – | States the backend revokes on |
No output schema declared.
No examples provided.
get_rule Get one rule ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The rule id, for example B1 |
No output schema declared.
No examples provided.
list_rules List the rule catalogue ~23
Every rule: id, group, severity, title and what it detects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
redact_text Redact a log ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salt | string | – | Mixed into the pseudonyms |
| text | string | yes | The text to redact |
No output schema declared.
No examples provided.
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 20 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 20 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.