Skip to content
ReapX logo

ReapX MCP server

Which servers in the official MCP registry are ReapX's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to ReapX

Whose server it is
  • Registry namedev.reapx/app-store-reviewsverified in the MCP registry

The registry name sits under reapx.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Staterequires sign-inchecked 2026-10-26

On 2026-10-26 the server answered and asked for a sign-in with a ReapX account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Signs in by OAuth: the client opens the sign-in on first connect.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer245 ms
  • Sign-inOAuth: the client signs you in

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "app-store-reviews": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=reapx/app-store-reviews-scraper"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http reapx https://mcp.apify.com/?actors=reapx/app-store-reviews-scraper

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.apify.com/?actors=reapx/app-store-reviews-scraper as a custom connector in the settings.

The first time it connects, the client opens a ReapX sign-in.

Other servers listed as ReapX's
  • dev.reapx/books-libraryanswers, requires sign-inverified in the MCP registry
  • dev.reapx/clinical-trialsanswers, requires sign-inverified in the MCP registry
  • dev.reapx/crypto-coingeckonot asked yetverified in the MCP registry
  • dev.reapx/discogs-musicnot asked yetverified in the MCP registry
  • dev.reapx/docker-containersnot asked yetverified in the MCP registry
  • dev.reapx/federal-registernot asked yetverified in the MCP registry
  • dev.reapx/github-reposnot asked yetverified in the MCP registry
  • dev.reapx/jobsnot asked yetverified in the MCP registry
  • dev.reapx/mastodon-fediversenot asked yetverified in the MCP registry
  • dev.reapx/npm-packagesnot asked yetverified in the MCP registry
  • dev.reapx/openfda-drug-recallsnot asked yetverified in the MCP registry
  • dev.reapx/public-sourcesnot asked yetverified in the MCP registry
  • dev.reapx/scientific-papersnot asked yetverified in the MCP registry
  • dev.reapx/sec-filingsnot asked yetverified in the MCP registry
  • dev.reapx/shopify-storesnot asked yetverified in the MCP registry
  • dev.reapx/stackoverflow-questionsnot asked yetverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.