Home / MCP registry index / net.apppage/app-data
AppPage.net - Google Play & App Store data
net.apppage/app-data in the official MCP registry.
Endpoint https://apppage.net/mcp.
The registry describes it as: Google Play & App Store app data: search, details, reviews, privacy, alternatives, top charts.
We read its 27 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_apps get_app find_alternatives browse_category get_app_reviews get_app_privacy get_developer_apps list_my_sites get_site check_subdomain create_site update_site get_page generate_page set_page set_app_ads_txt refresh_site_from_store get_modules set_module add_changelog_entry post_status_incident resolve_status_incident set_remote_config get_feedback set_app_links get_plan set_custom_domain
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/net-apppage-app-data)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.