SocialCrawl vs App Store Top Charts, Reviews & App Ideas (by flyingkiwi)
SocialCrawl is an MCP server published by RidioDevelopment. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). App Store Top Charts, Reviews & App Ideas (by flyingkiwi) is an MCP server published by flyingkiwi-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  SocialCrawl |  App Store Top Charts, Reviews & App Ideas (by flyingkiwi) |
|---|---|---|
| Official MCP Registry | Listed Version: 2.2.0 Downloads/month (npm): 1 329 Downloads/week (npm): 147 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 2.2.0 Downloads/month (npm): 1 329 Downloads/week (npm): 147 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | SocialCrawl | App Store Top Charts, Reviews & App Ideas (by flyingkiwi) |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-09 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (mcp.apify.com) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ridiodevelopment/socialcrawl-mcp | github.com/flyingkiwi-tools/apify-mcp-tools |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-11 | 2026-11-03 |
| Endpoint at the last check (differs) | Responded 24 h ago | Responded 5 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
SocialCrawl
One API for social, commerce, travel, jobs, finance and web data, with exact credit pricing.
App Store Top Charts, Reviews & App Ideas (by flyingkiwi)
Apple App Store top charts by country and category, rank changes, review themes and AI app ideas.
How to run each
SocialCrawl As a remote MCP server
claude mcp add --transport http socialcrawl https://mcp.socialcrawl.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: SOCIALCRAWL_API_KEY (secret), Authorization header
App Store Top Charts, Reviews & App Ideas (by flyingkiwi)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of App Store Top Charts, Reviews & App Ideas (by flyingkiwi) publish no settings it asks for, so we do not compare settings.
What it can do: SocialCrawl · What it can do: App Store Top Charts, Reviews & App Ideas (by flyingkiwi) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.