Apptiller
REMOTE · MCP.APPTILLER.COM · 2 COMPONENTS
Grow App Store apps: ranks, listing, ads, revenue and AI answers. Sign in to read your own apps.
Available components
Last scanned (13 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security81
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11066 tokens (~187/item across 59 items; 59 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 59 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
- Tool “campaigns” rewrote its description, which is the text the model reads security
- 18 Nov 26 0
- Tool “campaigns” rewrote its description, which is the text the model reads security
- 17 Nov 26 0
- New tool “campaigns” functional
- New tool “mark_move” functional
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Server version: 0.1.1 → 0.1.3 functional
- New tool “apple_ads_search_terms” functional
- 12 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “app_store_charts” rewrote its description, which is the text the model reads security
- Tool “app_store_drafts” rewrote its description, which is the text the model reads security
- Tool “app_store_funnel” rewrote its description, which is the text the model reads security
- Tool “app_store_keywords” rewrote its description, which is the text the model reads security
- Tool “app_store_listing” rewrote its description, which is the text the model reads security
- Tool “app_store_reviews” rewrote its description, which is the text the model reads security
- Tool “app_store_sales” rewrote its description, which is the text the model reads security
- Tool “apple_ads_accounts” rewrote its description, which is the text the model reads security
- Tool “apple_ads_performance” rewrote its description, which is the text the model reads security
- Tool “apply_proposal” rewrote its description, which is the text the model reads security
- Tool “apps” rewrote its description, which is the text the model reads security
- Tool “attribution_performance” rewrote its description, which is the text the model reads security
- Tool “attribution_setup” rewrote its description, which is the text the model reads security
- Tool “briefing” rewrote its description, which is the text the model reads security
- Tool “check_launch” rewrote its description, which is the text the model reads security
- Tool “close_site_guide” rewrote its description, which is the text the model reads security
- Tool “connect_account” rewrote its description, which is the text the model reads security
- Tool “data_coverage” rewrote its description, which is the text the model reads security
- Tool “dismiss_finding” rewrote its description, which is the text the model reads security
- Tool “edit_launch” rewrote its description, which is the text the model reads security
- Tool “launch_ai_answers” rewrote its description, which is the text the model reads security
- Tool “launch_product” rewrote its description, which is the text the model reads security
- Tool “list_connections” rewrote its description, which is the text the model reads security
- Tool “list_domains” rewrote its description, which is the text the model reads security
- Tool “list_launches” rewrote its description, which is the text the model reads security
- Tool “meta_ad_accounts” rewrote its description, which is the text the model reads security
- Tool “meta_diagnose” rewrote its description, which is the text the model reads security
- Tool “meta_performance” rewrote its description, which is the text the model reads security
- Tool “organic_todo” rewrote its description, which is the text the model reads security
- Tool “reject_proposal” rewrote its description, which is the text the model reads security
- Tool “revenuecat_chart” rewrote its description, which is the text the model reads security
- Tool “revenuecat_chart_options” rewrote its description, which is the text the model reads security
- Tool “revenuecat_overview” rewrote its description, which is the text the model reads security
- Tool “revenuecat_projects” rewrote its description, which is the text the model reads security
- Tool “revenuecat_revenue” rewrote its description, which is the text the model reads security
- Tool “set_app_brief” rewrote its description, which is the text the model reads security
- Tool “set_app_limits” rewrote its description, which is the text the model reads security
- Tool “set_site_guides” rewrote its description, which is the text the model reads security
- Tool “setup_suggestions” rewrote its description, which is the text the model reads security
- Tool “site_guides” rewrote its description, which is the text the model reads security
- Tool “undo_change” rewrote its description, which is the text the model reads security
- Tool “verify_domain” rewrote its description, which is the text the model reads security
- Tool “to_do” rewrote its description, which is the text the model reads security
- Tool “ai_referrals” rewrote its description, which is the text the model reads security
- Tool “ai_referrals_setup” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_collect” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_plan” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_report” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_run_now” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_set_questions” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_track” rewrote its description, which is the text the model reads security
- Tool “ai_visibility_tracked” rewrote its description, which is the text the model reads security
- Tool “app_brief” rewrote its description, which is the text the model reads security
- Tool “app_map_sources” rewrote its description, which is the text the model reads security
- Tool “app_ownership” rewrote its description, which is the text the model reads security
- Tool “app_performance” rewrote its description, which is the text the model reads security
- Tool “close_site_guide” is now declared destructive security
- Tool “dismiss_finding” is now declared destructive security
- Tool “launch_product” is now declared destructive security
- Tool “reject_proposal” is now declared destructive security
- Tool “set_site_guides” is now declared destructive security
- Schema quality: 163 → 183 ▼ functional
- 11 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ai_visibility_plan” rewrote its description, which is the text the model reads security
- Tool “launch_ai_answers” rewrote its description, which is the text the model reads security
- Tool “set_site_guides” rewrote its description, which is the text the model reads security
- Tool “site_guides” rewrote its description, which is the text the model reads security
- Schema quality: 142 → 163 ▼ functional
- New tool “app_store_drafts” functional
- New tool “app_store_charts” functional
- New tool “app_store_keywords” functional
- New tool “app_store_reviews” functional
- New tool “organic_todo” functional
- New tool “to_do” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.apptiller.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apptiller.com | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 146c071f0d4efd9d13ba8fb815082431 |
| SANs: apptiller.com, mcp.apptiller.com, *.mcp.apptiller.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.apptiller.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| apptiller.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.apptiller.com/.well-known/oauth-protected-resource/mcp", scope="mcp:read"
Bearer realm="OAuth", resource_metadata="https://mcp.apptiller.com/.well-known/oauth-protected-resource/mcp", scope="mcp:read" Protected resource metadata
| Document | https://mcp.apptiller.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.apptiller.com/mcp |
| Authorisation server | https://mcp.apptiller.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.apptiller.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.apptiller.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
revenuecat_revenue RevenueCat revenue ~103
Use this when the user asks how much revenue an app made between two dates, from RevenueCat. Total revenue for a RevenueCat project between two dates (inclusive): gross, net of taxes, or proceeds after store fees.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| end_date | string | yes | – |
| project_id | string | yes | RevenueCat project id (from revenuecat_projects). |
| revenue_type | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
set_app_brief Set an app's goal, markets and constraints ~239
Use this when the user states an app's goal, markets, competitors or constraints for Apptiller to work from. Writes the brief Apptiller's agent works from for one app. Fields left out stay as they are. goal: what a good result is, as a cost per paying subscriber, per trial or per install (with its currency) or a ROAS (revenue over spend, e.g. 1.2), or null to clear it. countries: the markets that matter most, as two-letter codes. competitors: apps the user names as competitors (names or App Store ids). constraints: plain words the agent must respect, such as a launch date or campaigns not to touch. facts: short facts by key (prices, seasonality, anything the agent should know); a null value removes one. The agent never overwrites what the user set here. These come from the user.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name or id (from apps). |
| competitors | array | – | – |
| constraints | – | – | – |
| countries | array | – | – |
| facts | array | – | – |
| goal | – | – | – |
No output schema declared.
No examples provided.
set_app_limits Set the limits Apptiller's agent works inside ~315
Use this only when the user asks to change how far Apptiller may go with an app's ad changes. Sets, for one app, how far Apptiller's agent may go. Owners and admins only. Fields left out stay as they are. mode: watch (the agent only reports), ask (it proposes changes and a member approves each one; the default) or autopilot. autopilot: it applies its own proposals inside these limits by itself, two changes a day at most (where the account's plan includes it; needs a linked ad account that is being read, an attribution source, and max_daily_increase unless the budget lever is off). max_step_pct: the biggest step one change may take, 1 to 50 percent of the current bid or budget (default 20). max_daily_increase: the most one change may add to a day's budget, in the ad account's currency (null: only the percentage applies). levers: which kinds of change the agent may propose (pause, budget, bid). protected_entities: campaign, ad set or keyword ids it must never propose to change. These limits also hold when a member applies a change, from here or the dashboard: one outside them is refused.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name or id (from apps). |
| levers | array | – | – |
| max_daily_increase | – | – | – |
| max_step_pct | integer | – | – |
| mode | string | – | – |
| protected_entities | array | – | – |
No output schema declared.
No examples provided.
set_site_guides Turn daily guides on or off ~135
Use this only when the user asks to turn website guides on or off. Turns daily guides on or off for one app's website. On needs the website verified, in a connected Google Search Console, and a plan that includes them; the error says which is missing. Each morning after that, Apptiller writes at most one guide, only when a search or question is worth one (otherwise it drafts the fix for a page Google shows but few click, in To do), and pauses while 3 wait unpublished.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name or id (from apps). |
| enabled | boolean | yes | – |
No output schema declared.
No examples provided.
setup_suggestions Suggested setup ~76
Use this when the user asks what to set up next in Apptiller, or why some numbers are missing. What this Apptiller account is still missing (connections to add or repair, settings in tools already used), each with why it helps and how to do it. Steps marked optional need a change in the user's app.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
site_guides Daily guides for an app's website ~453
Use this when the user asks about the guides Apptiller writes for their app's website. Daily guides for one app's website: whether they're on and what's missing to turn them on (a verified website in a connected Search Console, and a plan that includes them), and its guides, newest first. Each guide answers one need no page on the site answers: Google searches that show the site but are rarely clicked (the search and its numbers), a question Google's AI answers leave the app out of (its answers), or both. finding_id is the To do item's finding it was written for and finding_ids all of that item's findings (empty for guides written before items had findings): the need behind it, the title, address slug, meta description, the guide in Markdown with its two calls to action, the sentences to add on the site's own pages to link to it, and every claim the check read with what backs it (status held: something couldn't be backed; fix it before publishing). agent_spec is the whole job for a coding agent: where the page goes, its head tags and structured data, the links to add, the checks. Published guides carry their Google clicks and impressions since. Guides written from research also carry research (what they were written from, each part with its source and date or why it is missing: the site's Search Console searches on the topic, its App Store search terms, labelled as App Store demand and not Google volume, the tracked AI questions, the product's facts, the site's pages, Google's results and the top pages read, and Google search volume and difficulty), plan (the target searches by research id, the sections and the searches each serves, internal links from the site's pages, the FAQ), watch (the Google searches it targets) and, once published, watched (each of those searches' clicks, impressions and position on its address since). readiness.last_run says how the last morning run ended: a guide, the fix for a page's search finding drafted instead (its finding id), nothin…
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | App name or id (from apps). |
| limit | integer | – | – |
No output schema declared.
No examples provided.
to_do What to do next for the app ~283
Use this when the user asks what to do next for an app, or what is waiting for their approval. What to do next for an app, or for every app: the open items of Apptiller's To do list, best first, as the web app shows them. Splits: To approve (listing edits, App Store drafts, findings with a page or pitch to write, ad proposals), Review replies (reviews without an answer, with any drafted reply), Reach out (threads to join, lists to get onto) and New today (alerts). Each item has its app, kind, title, detail, why it is here, evidence, before and after text, what its action does (where it is written, whether it is public, whether it can be undone), due date, score, and locked: the plan feature its action needs when the account's plan lacks it. Snoozed and done items are left out. unavailable names any part that couldn't be read just now. Read-only: it approves, sends, rejects or marks nothing; each item carries the web app page where that is done.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | App name or id (from apps). Every app when left out. |
| limit | integer | – | – |
| split | string | – | approve, reply, outreach or watch (New today). All when left out. |
No output schema declared.
No examples provided.
undo_change Undo a change Apptiller made ~95
Use this only when the user asks to undo a change Apptiller made. Puts back, at the user's request, the value an ad account had before Apptiller changed it. Only while the campaign, ad group or keyword still has the value Apptiller wrote: if it was changed since, nothing is written. It changes the live ad account.
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string | yes | The change id, from briefing. |
No output schema declared.
No examples provided.
verify_domain Verify a domain ~128
Use this when the user wants to prove they own a domain. Starts proving the organization owns a domain, or checks it again: returns the TXT record to add at the domain's DNS provider (host and value), and whether Apptiller finds it now. Apptiller also looks for it every hour for 72 hours. Calling it again for the same domain keeps the same record. A verified domain proves an app is the organization's when the app's App Store listing points to it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain, e.g. damson.life. A pasted URL works too. |
No output schema declared.
No examples provided.
How do I install the Apptiller MCP server?
Apptiller is a hosted endpoint at https://mcp.apptiller.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.apptiller.com
claude mcp add --transport http com-apptiller-apptiller 'https://mcp.apptiller.com/mcp'
What is the Apptiller MCP server?
Apptiller is an MCP server listed in the public MCP registry as com.apptiller/apptiller. Grow App Store apps: ranks, listing, ads, revenue and AI answers. Sign in to read your own apps. This page covers its hosted endpoint (https://mcp.apptiller.com/mcp).
Is the Apptiller MCP server safe to use?
Apptiller scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Apptiller MCP server expose?
Apptiller exposes 59 tools: list_connections, setup_suggestions, connect_account, meta_ad_accounts, meta_diagnose, and 54 more. Their descriptions and schemas cost roughly 10,376 tokens of context every time the server is loaded.
Does the Apptiller MCP server require authentication?
Yes. Apptiller asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Apptiller MCP server still maintained?
Apptiller is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Apptiller MCP server?
VerifyMCP ran 12 checks on Apptiller, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Apptiller: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.