Dpd2

@Dpd2 list all purchases from the last 30 days and show me the top 3 products by revenue

Retrieved 47 purchases from your DPD account in the last 30 days. Top products by revenue: 1) 'Advanced WordPress Theme Bundle' ($2,340 across 18 purchases), 2) 'Premium Plugin Suite' ($1,890 across 12 purchases), 3) 'SEO Toolkit Pro' ($1,120 across 17 purchases). Total revenue for the period: $8,450. This is an illustrative example based on typical DPD purchase data structure.

This example combines the List DPD Purchases tool with AI synthesis to surface revenue insights. Requires valid API key with read access to purchase records. DPD's API returns paginated results, so large catalogs may need multiple requests. Date filtering helps keep response times reasonable.

@Dpd2 show me all storefronts and tell me which ones have active subscribers

Found 3 storefronts in your DPD account: 'Main Store' (142 subscribers), 'Beta Products' (23 subscribers), 'Free Resources' (0 subscribers). The Main Store has the most engagement with subscribers added as recently as yesterday. Beta Products shows steady growth over the past quarter. This is an illustrative example of how storefront and subscriber data would be presented together.

This example chains List Storefronts with List Subscribers for each storefront to provide a consolidated view. Useful for understanding which storefronts drive subscription revenue. Note that subscriber counts may include inactive subscriptions depending on your DPD settings—verify subscription status separately if needed.

@Dpd2 verify this webhook notification I just received and tell me what purchase it's reporting

Webhook signature verified successfully—this notification is authentic and originates from DPD. The notification reports a new purchase: Customer 'sarah.chen@example.com' purchased 'Mobile App UI Kit' for $79. Transaction ID: dpd_tx_8k3m9n2p. Payment processed via Stripe. You can safely process this purchase event in your fulfillment system. This is an illustrative example of webhook verification output.

This example demonstrates the Verify DPD Notification tool, which is critical for webhook security. You must pass both the original payload and signature from the HTTP headers. Without verification, you risk processing fraudulent purchase notifications. This is a write-side operation that confirms authenticity but doesn't modify data.

When Dpd2 fits for monthly subscriber billing audits

A 3-person SaaS team selling digital courses through DPD storefronts runs monthly revenue reconciliation. They pull subscriber lists and purchase records from the last 30 days, cross-check against Stripe, and flag discrepancies in a shared spreadsheet. Dpd2's List Subscribers and List DPD Purchases tools handle this in under two minutes—no manual CSV exports, no copy-paste errors. The API key setup takes five minutes. The trade-off: if you're running real-time subscription analytics or need sub-hour sync, Dpd2's pagination and date filters aren't built for streaming. But for monthly or weekly batch reconciliation at under 10k transactions, this MCP closes the loop without custom code. Worth the setup if you're already on DPD and tired of spreadsheet archaeology.

Why Dpd2 works for one-off purchase lookups

A two-person support team at a digital goods shop gets 15-20 tickets a day asking "where's my download link" or "did my payment go through." They used to log into the DPD dashboard, search by email, screenshot the purchase record, and paste it into the ticket. Now they query List DPD Customers or List DPD Purchases directly from Switchy, pull the transaction in seconds, and reply with proof. The Verify DPD Notification tool also lets them confirm webhook authenticity when a customer claims they never got a receipt email. The ceiling: if your ticket volume exceeds 100/day or you need CRM-level customer history stitching, Dpd2's seven tools won't replace a proper helpdesk integration. But for small-team triage where speed beats sophistication, this MCP cuts response time in half.

When Dpd2 handles weekly storefront audits

A solo creator running four DPD storefronts (ebooks, templates, courses, assets) checks each one weekly to confirm products are live, subscriber counts match expectations, and no webhook failures slipped through. Before Dpd2, this meant four browser tabs and a checklist. Now they run List Storefronts, Get Storefront for each ID, and DPD Ping API in a single Switchy session—takes three minutes, logs to a shared doc. The Verify DPD Notification tool catches any webhook signature mismatches before they escalate to missed sales. The limit: if you're managing 20+ storefronts or need automated alerting on inventory or uptime, Dpd2's toolset is too manual. But for creators with 2-5 storefronts doing weekly sanity checks, this MCP turns a 20-minute chore into a quick ritual.