MoneyBug Shopify Billing Integrity

io.github.kurious8282Published by GitHub account kurious8282v1.0.3Updated Oct 24, 2026

Shopify usage billing guard: App Events idempotency, retry risk, and cycle reconciliation.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote Apify-hosted MCP server that checks Shopify usage billing integrity: App Events idempotency, retry risk, and billing cycle reconciliation.

What you can do
Check Shopify App Events for idempotency issues and duplicate usage records. Assess retry risk in usage billing flows. Reconcile usage charges against billing cycles. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when auditing or debugging Shopify app usage-based billing, especially suspected duplicate charges, retry problems, or mismatches between recorded usage and a billing cycle.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com; OAuth authentication is required. No environment variables or headers are declared. Network access is needed.
Before you install
OAuth grants the server access on your behalf; review the scopes requested before authorizing. It concerns billing data, so treat any reconciliation output as advisory and verify against Shopify records. No tools are listed, so what it can read or change is not documented.

Installation

In SourceWeft

  1. Open MoneyBug Shopify Billing Integrity in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kurious8282%2Fmoneybug-shopify-billing-integrity/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "moneybug-shopify-billing-integrity": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=fetch-actor-details,moneybug/shopify-billing-integrity-api"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.3LatestOct 9, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.