Home / MCP registry index / com.apptiller/apptiller

Apptiller

com.apptiller/apptiller in the official MCP registry. Endpoint https://mcp.apptiller.com/mcp. Source: github.com/GPT-Genius-Lab/apptiller-mcp.

The registry describes it as: Grow App Store apps: ranks, listing, ads, revenue and AI answers. Sign in to read your own apps.

We read its 50 tools on 2026-11-09. 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 about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http apptiller https://mcp.apptiller.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "apptiller": {
      "url": "https://mcp.apptiller.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"apptiller","type":"http","url":"https://mcp.apptiller.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_connections setup_suggestions connect_account meta_ad_accounts meta_diagnose meta_performance apple_ads_accounts apple_ads_performance attribution_setup attribution_performance app_store_sales app_store_funnel revenuecat_projects revenuecat_overview revenuecat_revenue revenuecat_chart_options revenuecat_chart apps app_map_sources app_store_listing app_performance data_coverage briefing app_brief set_app_brief set_app_limits site_guides set_site_guides close_site_guide apply_proposal undo_change reject_proposal dismiss_finding launch_product list_launches check_launch edit_launch launch_ai_answers verify_domain list_domains app_ownership ai_visibility_track ai_visibility_set_questions ai_visibility_tracked ai_visibility_run_now ai_visibility_plan ai_visibility_collect ai_visibility_report ai_referrals_setup ai_referrals

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-09): 936213aab744bd29. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-apptiller-apptiller/badge.svg)](https://lazaretto.dev/mcp-registry/com-apptiller-apptiller)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.