Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+3 this week 71 Trust /100

Last scanned (18 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 631 tokens (~126/item across 5 items; 5 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

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 →

Changelog

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 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 0
    • Server version: 0.1.1 → 0.1.3 functional
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “about_apptiller” rewrote its description, which is the text the model reads security
    • Tool “free_app_check” rewrote its description, which is the text the model reads security
    • Tool “start_sign_up” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.1.0 → 0.1.1 functional
    • Tool “about_apptiller” changed its title: What Apptiller does and costs → What Apptiller does cosmetic
  • 8 Nov 26 66

    First indexed and scored.

Diagnostics

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/public

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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/public Verified 200
http (plaintext) http://mcp.apptiller.com/public Inconclusive 405
MCP tools · 5 exposed · ~576 tokens

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 →

Tool Tokens
about_apptiller ~42

What Apptiller does for App Store apps and their websites, what each feature needs, and how the owner connects or signs up. No sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browse_launches ~52

The current launch period's board on Apptiller Launches: each launch's name, tagline, category, verification tier and live rank (ranked by verified revenue added, never by votes), with its page.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

free_app_check ~135

A free public read of an App Store app (its link or id) or a website (its domain): the app's US listing facts (name, genre, rating), or what the site's home page shows search engines and whether it links to the App Store. Google Play is not supported. The full check (ranks for five searches, what ChatGPT names, a subtitle to try) runs once per account: the owner signs up and runs it from the returned page. One result per product is shared for 24 hours.

NameTypeReqDescription
linkstringyesApp Store link or id, or a website domain or URL.

No output schema declared.

No examples provided.

start_sign_up ~67

Emails the owner a link that makes their free Apptiller account (or signs them in to theirs). Nothing is made until they press it, within 24 hours. They can also sign in with Google when they add the connector.

NameTypeReqDescription
emailstringyesThe owner's email address.

No output schema declared.

No examples provided.

submit_launch ~280

Submits an app (its App Store link or id) or a website (its domain, plus a name) to Apptiller Launches for the owner. It is held, not public, until the owner opens the link emailed to them (within 24 hours), signs in or makes an account, and confirms it. Once confirmed it is listed as not verified; it shows as the verified owner's once they prove they own it (an App Store Connect key, or a TXT record on the website's domain), and it is ranked once its RevenueCat (app) or Stripe (website) is connected, by the revenue it adds in its launch period. A product launches once per account, and one proven by its owner can't be launched by anyone else. Launching is free; it makes the product's name, tagline and launch-period numbers public.

NameTypeReqDescription
categorystringyes–
emailstringyesThe owner's email address.
hide_amountsboolean–Show rank and growth only, never dollar amounts.
kindstringyes–
linkstringyesApp 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.
taglinestringyesWhat it does, in one line.

No output schema declared.

No examples provided.

Install

How do I install the Apptiller MCP server?

Apptiller is a hosted endpoint at https://mcp.apptiller.com/public, 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

# add to Claude Code
claude mcp add --transport http com-apptiller-apptiller 'https://mcp.apptiller.com/public'
Common questions

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/public).

Is the Apptiller MCP server safe to use?

Apptiller scores 71 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 5 tools: about_apptiller, free_app_check, browse_launches, start_sign_up, submit_launch. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.

Does the Apptiller MCP server require authentication?

No. We connected to Apptiller without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.