App Store Reviews Scraper: iOS app reviews, ratings, details

io.github.bepolabsPublished by GitHub account bepolabsv1.0.0Updated Nov 12, 2026

iOS app reviews, ratings, details, as one MCP tool through Apify

The publisher's own server: details.page

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

An Apify-hosted MCP server that lets an assistant collect iOS App Store reviews, ratings and app details through a single tool.

What you can do
  • Collect iOS App Store reviews for an app
  • Retrieve app ratings and app detail information
  • Run the collection as one Apify actor tool through the hosted MCP endpoint
When to use it
Useful when you want an assistant to pull App Store review and rating data for a specific iOS app, for example to summarize user feedback or compare apps, without building your own scraper.
Requirements
Remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Apify API token sent as an Authorization header in the form Bearer token, or sign-in through OAuth. An Apify account is implied.
Before you install
The Authorization header carries an Apify API token, a credential that should be kept secret and scoped appropriately. Runs are executed on Apify's platform, so requests and target app identifiers are sent to that third party, and Apify usage may be billed to your account.

Installation

In SourceWeft

  1. Open App Store Reviews Scraper: iOS app reviews, ratings, details 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.bepolabs%2Fapp-store-reviews/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": {
    "app-store-reviews-scraper-ios-app-review": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bepolabs/app-store-reviews"
    }
  }
}

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.0LatestNov 12, 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.

Other Details integrations