
MoneyBug Shopify Monetization Intelligence
io.github.kurious8282Published by GitHub account kurious8282v1.0.2Updated Oct 24, 2026
Shopify app monetization: pricing, usage fees, percentage billing, and M&A fingerprints.
Overview
A remote Apify-hosted MCP server that gives an assistant Shopify app monetization intelligence: pricing, usage fees, percentage billing and M&A fingerprints.
- What you can do
- Retrieve Shopify app monetization signals covering pricing structures and usage fees, according to the registry description. Look into percentage-based billing arrangements for Shopify apps. Examine M&A fingerprints related to Shopify app monetization. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Useful when researching how Shopify apps price and monetize, comparing billing models such as usage fees or percentage billing, or looking for acquisition and M&A signals in the Shopify app ecosystem.
- Requirements
- Runs as a remote streamable HTTP endpoint at mcp.apify.com; no local package is needed. OAuth authentication is required. No environment variables or headers are declared.
Installation
In SourceWeft
- Open MoneyBug Shopify Monetization Intelligence in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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-monetization-intelligence/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"moneybug-shopify-monetization-intelligen": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,moneybug/shopify-app-monetization-intelligence"
}
}
}Tools
0Version history
1- v1.0.2LatestOct 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.