Analyzed 34 days ago · 2 anonymous rescans remaining · register free to re-analyze any time.
Public analysis · read only
Register free to re-analyze

JiantaoFu/AppInsightMCP

24 14 1 issues
JavaScript
MIT

Project Overview

anthropic / claude-opus-4-7

AppInsightMCP

MCP server exposing Apple App Store and Google Play scraper APIs as tools for AI assistants.

AI Verdict
Clean— AI Trust Assessment

True Intent (AI Assessment)

Expose Apple App Store and Google Play scraping capabilities as MCP tools so AI assistants can retrieve app metadata, reviews, and rankings.

README Accuracy

Accurate

Notes

Code matches the README description. The only caveat is inherent to any store scraper — reliance on unofficial scraping of Apple/Google endpoints may violate their ToS and can break without notice.

What Is This?

AppInsightMCP is a Model Context Protocol (MCP) server written in JavaScript that wraps two existing scraper libraries (@jeromyfu/app-store-scraper and @jeromyfu/google-play-scraper) and exposes their functionality as MCP tools. It runs as a stdio-based server that AI clients like Claude Desktop can connect to in order to query mobile app marketplace data.

The problem it addresses is that large language models have no built-in way to fetch live data about mobile apps — details, rankings, reviews, ratings, similar apps, privacy info, permissions, and so on. Rather than each user writing custom scraping code, this server provides a ready-made bridge so an AI assistant can answer questions about apps in the Apple App Store and Google Play Store on demand.

The intended users are developers, product managers, marketers, or researchers who want to use an AI assistant (via MCP) to perform app market intelligence — competitor research, review analysis, category exploration, and trend tracking. Users install it via npx, Docker, or Smithery and configure it in their MCP client's config file.

Internally, the implementation is straightforward: a single src/server.js file registers roughly 20 tools (10 for App Store, 10 for Google Play) using the @modelcontextprotocol/sdk. Each tool defines a Zod schema for parameters, calls the corresponding scraper library function, and returns the JSON result as text. Communication uses StdioServerTransport, so it's driven by the parent MCP client process. A Dockerfile provides a production build using node:22-alpine.

No obvious red flags. The code is a thin, transparent wrapper over public scraper libraries; there is no telemetry, no network calls beyond the scrapers themselves, and no credential handling. Users should be aware that the underlying libraries scrape public store pages, which may be subject to rate limiting or terms-of-service considerations from Apple/Google.

Your Report, Tab by Tab
At a Glance
24Stars
14Forks
1Open Issues
December 8, 2025Last Active
MCP Server (CLI Tool)JavaScriptMIT
Technology Stack
LanguagesJavaScript, Dockerfile
RuntimeNode.js 18+ (Docker image uses Node 22)
FrameworkModel Context Protocol SDK
DatabaseNone
Package Managernpm
Key Dependencies@modelcontextprotocol/sdk, @jeromyfu/app-store-scraper, @jeromyfu/google-play-scraper, zod, punycode
Build ToolNone (plain Node ESM); Docker for containerization
Test FrameworkMocha + Chai (declared, no test files visible)