MCP Tools Directory
← Browse integrations

Developer tools

io.github.lazytitan30/billing-doctor

Free account · sign-in required

Contact io.github.lazytitan30/billing-doctor

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

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

Transport
stdio
Authentication
none
Initial setup
none
Runtime
unattended
Evidence
documented
Version
0.1.1
Package
billing-doctor
Last compatibility test
Not independently tested

Connect your agent

billing-doctor

Publisher README and package manifest reviewed from pinned captures. The package was not executed. The qualified core is the local stdio MCP mode; the optional credentialed --fetch CLI path remains outside this connection classification.

Capabilities: Diagnose Google Play Billing timelines, Explain subscription state, Decode real-time developer notifications, Redact sensitive log text, List and explain diagnostic rules

Connected profiles

Additional details

Registry identifier

io.github.lazytitan30/billing-doctor

Source ↗ · Checked 2026-09-17
Published version

0.1.1

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

billing-doctor

Source ↗ · Checked 2026-09-19
Source manifest version

0.1.1

Source ↗ · Checked 2026-09-19
Unattended configuration

The billing-doctor mcp command serves six local tools over stdio and can be launched as an MCP client subprocess.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

The default local MCP workflow requires no authentication or network service. The separately documented optional diagnose --fetch CLI feature uses a Google service-account key and is not part of this default connection classification.

Source ↗ · Checked 2026-09-19
Connection configuration

Configure the MCP client to run npx with -y, billing-doctor, and mcp arguments over stdio.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19