Skip to content

MCP servers › com.apptiller › apptiller

MCP server · registry snapshot 2026-11-12 · last tested 2026-11-12

apptiller MCP server

Registry name com.apptiller/apptiller

by apptiller.com · domain (the registry's namespace rule)repository owner on GitHub: GPT-Genius-Lab (organization)Source ↗Website ↗

Grow App Store apps: ranks, listing, ads, revenue and AI answers. Sign in to read your own apps. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-12version 0.1.3JavaScriptstreamable HTTP56 tools

Summary

com.apptiller/apptiller is a remote MCP server listed in the official MCP registry at version 0.1.3, under the namespace of the domain apptiller.com. Its linked repository is github.com/GPT-Genius-Lab/apptiller-mcp; GitHub reports its owner as GPT-Genius-Lab, an organization. On 2026-11-12 ProtocolProbe connected to it in read-only mode and read its inventory: 56 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
56
Last tested
2026-11-12

Tool list size

23,933 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (56 tools). Counted with Anthropic's token counter on 2026-11-12, from the tool list we read on 2026-11-12. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-12 (mcp.apptiller.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.1.3).

Add to your client

Observed fact

This server accepted a session without any credential and lists 17 tools whose name or declaration suggests they change data (attribution_setup, app_map_sources, app_store_listing, set_app_brief, set_app_limits and 12 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-12.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-12
Mode
read-only (no tool calls)
Latest version
0.1.3, published 2026-11-09 (registry, as of the 2026-11-12 snapshot)
First listed version
2026-11-08 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, 2026-11-08 to 2026-11-09; 4 in the 90 days before the 2026-11-12 snapshot.
Most recent 4 versions
  • 0.1.3 · 2026-11-09
  • 0.1.2 · 2026-11-09
  • 0.1.1 · 2026-11-09
  • 0.1.0 · 2026-11-08
(versions still listed in the registry only)
Registry data
snapshot 2026-11-12
Package and repository
checked 2026-11-12
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.1.1 (published 2026-11-09) → 0.1.3 (published 2026-11-09), between the registry lists of 2026-11-09 and 2026-11-12.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12; release notes from the GitHub Releases API, checked 2026-11-12.

What it is

What does this server offer?

Observed inventory
56tools
0resources
0prompts

None of its 56 tools are described as changing anything. For 56 the reading was uncertain, so no mark is shown.

  • list_connectionson 28 other servers

    “Use this when the user asks which services are connected to Apptiller.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • setup_suggestions

    “Use this when the user asks what to set up next in Apptiller, or why some numbers are missing.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • connect_accounton 21 other servers

    “Use this when the user wants to connect a service to Apptiller: App Store Connect, an ad account, an attribution tool, RevenueCat, Stripe or Google Search Console.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input, 1 required
    • providerstringrequired“The service to connect.”
  • meta_ad_accountson 1 other server

    “Use this when the user asks which Meta ad accounts Apptiller can read.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • meta_diagnose

    “Use this when Meta data is missing or a Meta account can't be read.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • meta_performance

    “Use this when the user asks how their Meta (Facebook, Instagram) ads are doing.”

    Publisher declares: read-only yes · destructive no · open-world no

    6 inputs, 1 required
    • account_idstringrequired“Ad account id, e.g.”
    • levelstring
    • date_presetstring
    • sincestring
    • untilstring
    • rawboolean“Return every Meta action type instead of the summary.”
  • apple_ads_accounts

    “Use this when the user asks which Apple Ads accounts Apptiller can read.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • apple_ads_performance

    “Use this when the user asks how their Apple Ads campaigns, ad groups or keywords are doing, as Apple reports them.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 2 required
    • levelstring
    • sincestringrequired“First day (inclusive), in the ad account's reporting timezone.”
    • untilstringrequired“Last day (inclusive).”
    • campaign_idstring
    • rawboolean
  • attribution_setup

    “Use this only when the user asks to set up Apple Ads attribution for an app that has no attribution or revenue SDK.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    Takes no inputs.

  • attribution_performance

    “Use this when the user asks which network, campaign or keyword brought installs, as the attribution tool counted them.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs, 2 required
    • levelstring
    • sincestringrequired“First day (inclusive), UTC.”
    • untilstringrequired“Last day (inclusive).”
  • app_store_saleson 1 other server

    “Use this when the user asks about an app's downloads, sales, proceeds or refunds.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 2 required
    • sincestringrequired“First day (inclusive), Pacific Time.”
    • untilstringrequired“Last day (inclusive).”
    • appstring“An Apptiller app (name or id from apps) or an App Store Apple ID.”
    • bystring“day: one row per app and day; country: per storefront over the range; product: per in-app purchase or subscription (and the app itself) over the range.”
    • countrystring“Only this storefront, e.g.”
  • app_store_funnel

    “Use this when the user asks where an app's downloads came from (search, browse, websites, other apps) or about impressions, page views and conversion.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 2 required
    • sincestringrequired“First day (inclusive), UTC.”
    • untilstringrequired“Last day (inclusive).”
    • appstring“An Apptiller app (name or id from apps) or an App Store Apple ID.”
    • bystring“day: one row per app and day; source: per source type over the range; country: per territory over the range.”
    • countrystring“Only this territory, as Apple names it in the reports (e.g.”
Show 44 more tools
  • revenuecat_projects

    “Use this when the user asks which RevenueCat projects Apptiller can read.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • revenuecat_overview

    “Use this when the user asks for an app's current subscription numbers, such as MRR, active subscriptions or trials.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 1 required
    • project_idstringrequired“RevenueCat project id (from revenuecat_projects).”
    • currencystring
  • revenuecat_revenue

    “Use this when the user asks how much revenue an app made between two dates, from RevenueCat.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 3 required
    • project_idstringrequired“RevenueCat project id (from revenuecat_projects).”
    • start_datestringrequired
    • end_datestringrequired
    • currencystring
    • revenue_typestring
  • revenuecat_chart_options

    “Use this before building a RevenueCat chart, to see what it accepts.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs, 2 required
    • project_idstringrequired“RevenueCat project id (from revenuecat_projects).”
    • chart_namestringrequired
    • realtimeboolean
  • revenuecat_chart

    “Use this when the user asks how a subscription metric (trials, conversion, MRR, churn, retention) moved over time.”

    Publisher declares: read-only yes · destructive no · open-world no

    11 inputs, 2 required
    • project_idstringrequired“RevenueCat project id (from revenuecat_projects).”
    • chart_namestringrequired
    • start_datestring
    • end_datestring
    • resolutionstring“Resolution id from revenuecat_chart_options, e.g.”
    • segmentstring“Segment id from revenuecat_chart_options.”
    • limit_num_segmentsinteger
    • filtersarray
    • selectorsobject
    • currencystring
    • realtimeboolean
  • “Use this when the user asks which apps are in their Apptiller account, or which accounts feed each app.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • app_map_sources

    “Use this when the user wants to add an app to Apptiller or link an ad account, attribution app or RevenueCat project to it.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    7 inputs, 1 required
    • appstringrequired“App name or id, e.g.”
    • createboolean“Create the app if it does not exist.”
    • app_store_idstring
    • bundle_idstring“iOS bundle id; used to find the App Store listing when the App Store id is not known.”
    • play_packagestring
    • addarray
    • removearray
  • app_store_listingon 1 other server

    “Use this when the user asks what an app's App Store listing says or what changed in it.”

    Publisher declares: read-only no · destructive no · open-world yes

    4 inputs, 1 required
    • appstringrequired“App name or id (from apps).”
    • refreshboolean“Look the listing up now instead of showing the last daily check.”
    • countrystring“Storefront, e.g.”
    • daysinteger“How far back to list changes.”
  • app_performance

    “Use this when the user asks about one app's ad spend, installs, revenue, ROAS or cost per install across ad networks.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 3 required
    • appstringrequired“App name or id (from apps).”
    • sincestringrequired“First day (inclusive).”
    • untilstringrequired“Last day (inclusive).”
    • breakdownstring
    • per_dayboolean
  • data_coverageon 3 other servers

    “Use this before judging ad campaigns by revenue or paying users, or when the user asks what their data can show.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • “Use this when the user asks what's wrong with their ads, what to change, or what an earlier ad change did.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs
    • appstring“App name or id (from apps).”
    • refreshboolean“Run the analysis now instead of showing the last daily run.”
  • app_brief

    “Use this when the user asks what goal, markets, constraints or limits Apptiller works from for an app.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • appstringrequired“App name or id (from apps).”
  • set_app_brief

    “Use this when the user states an app's goal, markets, competitors or constraints for Apptiller to work from.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs, 1 required
    • appstringrequired“App name or id (from apps).”
    • goalobject or null
    • countriesarray
    • competitorsarray
    • constraintsstring or null
    • factsarray
  • set_app_limits

    “Use this only when the user asks to change how far Apptiller may go with an app's ad changes.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    6 inputs, 1 required
    • appstringrequired“App name or id (from apps).”
    • modestring
    • max_step_pctinteger
    • max_daily_increasenumber or null
    • leversarray
    • protected_entitiesarray
  • site_guides

    “Use this when the user asks about the guides Apptiller writes for their app's website.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 1 required
    • appstringrequired“App name or id (from apps).”
    • limitinteger
  • organic_todo

    “Use this when the user asks what to do to show up more in Google search or AI answers.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 1 required
    • appstringrequired“App name or id (from apps).”
    • limitinteger
  • to_do

    “Use this when the user asks what to do next for an app, or what is waiting for their approval.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs
    • appstring“App name or id (from apps).”
    • splitstring“approve, reply, outreach or watch (New today).”
    • limitinteger
  • app_store_keywords

    “Use this when the user asks which App Store searches an app ranks for, or how its keyword ranks moved.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs, 1 required
    • appstringrequired“App name or id (from apps).”
    • countrystring“Only this storefront, e.g.”
    • include_droppedboolean“Also list the terms that were dropped.”
  • app_store_charts

    “Use this when the user asks where an app sits in the App Store top charts, or why it moved.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • appstringrequired“App name or id (from apps).”
  • app_store_reviewson 4 other servers

    “Use this when the user asks what reviewers say about an app, which reviews need an answer, or how its ratings are trending.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • appstringrequired“App name or id (from apps).”
  • app_store_drafts

    “Use this when the user asks about proposed App Store listing edits, featuring nominations, in-app events or custom product pages.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • appstringrequired“App name or id (from apps).”
  • set_site_guides

    “Use this only when the user asks to turn website guides on or off.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 2 required
    • appstringrequired“App name or id (from apps).”
    • enabledbooleanrequired
  • close_site_guide

    “Use this when the user says a guide went live, or wants to drop it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    3 inputs, 2 required
    • guide_idstringrequired“The guide id, from site_guides.”
    • statusstringrequired
    • urlstring
  • apply_proposalon 1 other server

    “Use this only after the user has seen a specific proposal and said to apply it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • proposal_idstringrequired“The proposal id, from briefing.”
  • “Use this only when the user asks to undo a change Apptiller made.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • change_idstringrequired“The change id, from briefing.”
  • reject_proposalon 2 other servers

    “Use this when the user declines one of the analyst's proposals.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • proposal_idstringrequired“The proposal id, from briefing.”
  • dismiss_finding

    “Use this when the user wants a finding to stop coming up.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • finding_idstringrequired“The finding id, from briefing.”
  • launch_producton 1 other server

    “Use this when the user asks to launch their app or website on Apptiller Launches.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    6 inputs, 4 required
    • kindstringrequired
    • linkstringrequired“App Store link or id for an app; domain or URL for a website.”
    • namestring“Required for a website; an app's defaults to its App Store name.”
    • taglinestringrequired“What it does, in one line.”
    • categorystringrequired
    • hide_amountsboolean“Show rank and growth only, never dollar amounts.”
  • list_launcheson 7 other servers

    “Use this when the user asks how their launches on Apptiller Launches are doing.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • check_launch

    “Use this after the user connects or proves something that could change a launch's tier.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • launch_idstringrequired“From list_launches.”
  • edit_launch

    “Use this when the user asks to change how a launch shows on the board.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    5 inputs, 1 required
    • launch_idstringrequired“From list_launches.”
    • namestring
    • taglinestring
    • categorystring
    • hide_amountsboolean
  • launch_ai_answers

    “Use this when the user asks whether AI answers name their launched product.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs, 1 required
    • launch_idstringrequired“From list_launches.”
    • questionsarray
    • runboolean“Start the first check (once per launch).”
    • countrystring“With run: the country the answers are asked from, kept for the daily runs; usually where the maker's buyers are.”
    • rawboolean“Include the latest day's answers: text, names, cited pages.”
  • verify_domainon 20 other servers

    “Use this when the user wants to prove they own a domain.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • domainstringrequired“The domain, e.g.”
  • “Use this when the user asks which domains are verified.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • app_ownership

    “Use this when the user asks whether Apptiller sees an app as theirs, or how to prove it.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • appstringrequired“App name or id, e.g.”
  • ai_visibility_track

    “Use this when the user wants to start tracking whether AI assistants recommend their app.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    10 inputs, 2 required
    • projectstringrequired“Project name or id, e.g.”
    • aliasesarrayrequired“Names the app goes by in answers, e.g.”
    • domainsarray“The app's own sites, e.g.”
    • app_store_idstring
    • play_packagestring
    • competitorsarray
    • countrystring“Where the questions are asked from, e.g.”
    • languagestring“e.g.”
    • enginesarray
    • runs_per_dayinteger“How many times a day each question is asked on each engine (0 pauses the daily runs).”
  • ai_visibility_set_questions

    “Use this when the user wants to add or change the questions AI answers are checked for.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 2 required
    • projectstringrequired
    • questionsarrayrequired
    • replaceboolean
  • ai_visibility_tracked

    “Use this when the user asks which apps and questions are tracked in AI answers.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • ai_visibility_run_now

    “Use this when the user asks for fresh AI answers now instead of waiting for the daily run.”

    Publisher declares: read-only no · destructive no · open-world yes

    1 input, 1 required
    • projectstringrequired
  • ai_visibility_plan

    “Use this when the user asks how many apps, questions or runs their AI-answer tracking covers.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • ai_visibility_collect

    “Use this after asking the questions again, to fetch the answers that are ready.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • ai_visibility_reporton 1 other server

    “Use this when the user asks whether ChatGPT or Google's AI answers recommend their app, and who they name instead.”

    Publisher declares: read-only yes · destructive no · open-world no

    3 inputs, 1 required
    • projectstringrequired
    • daysinteger
    • by_questionboolean
  • ai_referrals_setup

    “Use this when the user wants to count visitors that AI assistants send to their website.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 1 required
    • projectstringrequired
    • domainsarray
  • ai_referrals

    “Use this when the user asks how many visitors AI assistants sent to their website.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 1 required
    • projectstringrequired
    • daysinteger

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-12.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
52% of 139
Tools with a description
100% of 56
Typical description length
597 characters

The tool set

Counted from the listing

Tools
56
Size of the list
about 17,327 tokens for an agent to load (characters ÷ 4)
Naming
54 of 56 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 56 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.apptiller.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "apptiller": {
      "url": "https://mcp.apptiller.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "apptiller": {
      "type": "http",
      "url": "https://mcp.apptiller.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"apptiller","type":"http","url":"https://mcp.apptiller.com/mcp"}'
Claude Code
claude mcp add --transport http apptiller https://mcp.apptiller.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "apptiller": {
      "type": "streamableHttp",
      "url": "https://mcp.apptiller.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "apptiller": {
      "httpUrl": "https://mcp.apptiller.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.apptiller]
url = "https://mcp.apptiller.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "apptiller": {
      "url": "https://mcp.apptiller.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.apptiller.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.

Own host

  • security.txt. No security.txt at https://mcp.apptiller.com/.well-known/ (HTTP 404, 2026-11-12). security.txt found at https://apptiller.com/.well-known/security.txt (Contact given; expires 2027-11-07). Source: mcp.apptiller.com/.well-known/security.txt · read 2026-11-12.
  • A2A agent card. No A2A agent card at https://mcp.apptiller.com/.well-known/ (HTTP 404, 2026-11-12). No A2A agent card at https://apptiller.com/.well-known/ (HTTP 404, 2026-11-12). Source: mcp.apptiller.com/.well-known/agent-card.json · read 2026-11-12.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.apptiller.com/mcpSession openedmatchesour test · 2026-11-12
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-12
Repository github.com/GPT-Genius-Lab/apptiller-mcpOpens publiclymatchesapi.github.com · 2026-11-12

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.apptiller
GitHub owner
an organization (GPT-Genius-Lab)
Repository
github.com/GPT-Genius-Lab/apptiller-mcp
Stars
1
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-12; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint mcp.apptiller.com/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-09 to 2026-11-12; versions 0.1.1 to 0.1.3).

Last change seen between our reads on 2026-11-09 (version 0.1.1) and 2026-11-12 (version 0.1.3).

Added (6):

app_store_chartsapp_store_draftsapp_store_keywordsapp_store_reviewsorganic_todoto_do

Changed (50) (25 shown):

ai_referrals: description, annotationsai_referrals_setup: description, annotationsai_visibility_collect: descriptionai_visibility_plan: title, description, annotationsai_visibility_report: description, annotationsai_visibility_run_now: descriptionai_visibility_set_questions: description, annotationsai_visibility_track: description, annotationsai_visibility_tracked: description, annotationsapp_brief: description, annotationsapp_map_sources: description, annotationsapp_ownership: description, annotationsapp_performance: description, annotationsapp_store_funnel: description, annotationsapp_store_listing: description, annotationsapp_store_sales: description, annotationsapple_ads_accounts: description, annotationsapple_ads_performance: description, annotationsapply_proposal: description, annotationsapps: description, annotationsattribution_performance: description, annotationsattribution_setup: description, annotationsbriefing: description, annotationscheck_launch: descriptionclose_site_guide: description, annotations

and 25 more.

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-12 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.apptiller/apptiller

Answered from the data above

Who publishes com.apptiller/apptiller?

The registry ties the namespace com.apptiller to the domain apptiller.com; only its owner can publish under it. Its linked repository is github.com/GPT-Genius-Lab/apptiller-mcp; GitHub reports its owner as GPT-Genius-Lab, an organization. These are facts from the registry and GitHub, not a rating.

Is com.apptiller/apptiller safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.apptiller/apptiller need an API key or sign-in?

It opened a session without any credential on 2026-11-12. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.apptiller/apptiller been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does com.apptiller/apptiller publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.apptiller/apptiller?

In github.com/GPT-Genius-Lab/apptiller-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-12
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-12, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,412 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 56 tools, 0 resources, 0 prompts.
  4. 8,852 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-12; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-12
Hosting type
registry · 2026-11-12
MCP capability
tools
our test · 2026-11-12
Transport
streamable HTTP
registry · 2026-11-12
Required credentials
none declared
registry · 2026-11-12 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-12
Lifecycle status
registry · 2026-11-12
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-12
Maintenance
api.github.com · 2026-11-12
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-12

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.apptiller/apptiller: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/com.apptiller/apptiller

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.apptiller/apptiller)](https://protocolprobe.com/mcp/servers/com.apptiller/apptiller)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology