Company
- Product: MRRdue, at www.mrrdue.com
- Operated by: Akash Yadav, a sole proprietor registered as an MSME (Udyam) in Balrampur, Uttar Pradesh, India
- Team location: the founder works from Bengaluru, India
- Founder: Akash Yadav (@akashyadav_dev on X)
- Started: development began in June 2026
- Funding: bootstrapped, no outside investment
- Contact: support@mrrdue.com
What MRRdue does
MRRdue connects to Stripe and Dodo Payments with read-only access, finds every failed payment, ranks it by the revenue at risk, explains why it failed, and prepares the recovery email. A founder works down that list instead of digging through a billing dashboard. You can try the whole flow on sample data, with no signup, on the homepage demo or the full demo dashboard.
How MRRdue uses Claude
MRRdue ships a native Model Context Protocol (MCP) server. Claude, Claude Code, and other MCP clients connect over OAuth 2.1 and call MRRdue tools such as who_needs_attention, get_metrics, list_at_risk_customers, get_recovery_email, forecast_mrr and bulk_preview. A founder asks in plain language which payments to recover first and why, and Claude answers from their live billing data and drafts a batch of recovery emails.
The safety line is deliberate. An assistant can read data and draft a batch, but only a signed-in person can approve one, and nothing an assistant does can touch the billing account. See the MCP docs and the security page.