App Pain API
REMOTE · HAWKMILL.COM
What users hate about ANY iOS/Android app: clustered complaints, evidence, trends. No key needed.
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
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 Security69
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1445 tokens (~206/item across 7 items; 7 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 4 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.
- 2 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 69
First indexed and scored.
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 5 Nov 2026 · Probed https://hawkmill.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hawkmill.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 75f6a4463084012f132f588df5f4b5e6 |
| SANs: hawkmill.com, www.hawkmill.com, *.www.hawkmill.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 hawkmill.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hawkmill.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hawkmill.com/mcp | Verified | 200 | |
| http (plaintext) | http://hawkmill.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 →
get_app_details App details ~124
App metadata: name, developer, category, price, average rating, rating count and 1-5★ histogram (when available).
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store or Google Play URL, iOS numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps |
| country | string | – | ISO country code, default "us" |
| store | string | – | optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android) |
No output schema declared.
No examples provided.
get_app_reviews Raw reviews ~171
Fetch raw app reviews (unified schema across stores: rating/title/body/version/date/devReply/thumbsUp), 50 per page. Use for drill-down after mine_app_pain_points.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store or Google Play URL, iOS numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps |
| country | string | – | ISO country code, default "us" |
| page | integer | – | page number, default 1 (50/page) |
| sort | string | – | default recent (Android only; iOS uses the store default order) |
| store | string | – | optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android) |
No output schema declared.
No examples provided.
get_pain_trend Pain-point trend ~182
How an app's pain points changed over time: compares two archived analyses and labels each theme new / resolved / rising / falling / stable with share deltas (percentage points). Instant (archive read, no LLM). Default: latest vs ~30 days earlier. Returns a note when the app has fewer than two snapshots yet.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store or Google Play URL, iOS numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps |
| from | string | – | baseline date YYYY-MM-DD (optional) |
| store | string | – | optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android) |
| to | string | – | comparison date YYYY-MM-DD (optional, default newest) |
No output schema declared.
No examples provided.
get_version_history Version history ~140
Per-version review stats (review count, average rating, first/last seen) — spot a rating crash right after a bad release. Android: aggregated from recent reviews. iOS: current version + release notes.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store or Google Play URL, iOS numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps |
| country | string | – | ISO country code, default "us" |
| store | string | – | optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android) |
No output schema declared.
No examples provided.
mine_app_pain_points Mine app pain points ~337
THE core tool: fetch recent reviews of any iOS/Android app, keep the negative ones, and cluster them into ranked pain points (title, sharePercent, severity 1-5, verbatim evidence quotes). Ideal for competitive research and product discovery. Cached 7 days (instant on repeat); a COLD server-side analysis takes 30-120s. If the result has "mode":"agent", it contains prepared negative reviews and "instructions" — do the clustering yourself and present it to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| analyze | string | – | who clusters on a cold run: "server" = our model; "agent" = you get the prepared negative reviews + instructions and cluster them with your own model; "auto" (default) = server, switching to agent wh… |
| appId | string | yes | App Store or Google Play URL, iOS numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps |
| country | string | – | ISO country code, default "us" |
| maxRating | integer | – | ratings <= this count as negative, default 3 |
| model | string | – | premium refinement model (paid keys only). Omit for the free default. |
| reviews | integer | – | reviews to analyze, default 300 (other values round up to these tiers; iOS depth is ~50 due to Apple edge limits) |
| store | string | – | optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android) |
No output schema declared.
No examples provided.
search_apps Search apps ~110
Search the iOS App Store and Google Play (both merged by default) to find apps and their ids. Use this FIRST when you only know an app name or a category.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO country code, default "us" |
| limit | integer | – | max results per store, default 10 |
| q | string | yes | search query, e.g. "habit tracker" or "notion" |
| store | string | – | limit to one store (default: both merged) |
No output schema declared.
No examples provided.
watch_competitors Watch competitors (alerts) ~167
Continuous competitor monitoring (paid plans: Starter 2 apps weekly, Pro 15 apps daily). Manage the watchlist and the alert destination; digests of NEW 1-2★ reviews and NEW/RISING pain points are pushed to a Slack / Discord / any https webhook. action: list | add | remove | set_webhook | test.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| appId | string | – | for add/remove: store URL, iOS id or Android package |
| store | string | – | optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android) |
| webhookUrl | string | – | for set_webhook (or add): https URL, e.g. a Slack incoming webhook or Discord channel webhook |
No output schema declared.
No examples provided.
How do I install the App Pain API MCP server?
App Pain API is a hosted endpoint at https://hawkmill.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 · hawkmill.com
claude mcp add --transport http apppainapi-app-pain-api 'https://hawkmill.com/mcp'
What is the App Pain API MCP server?
App Pain API is an MCP server listed in the public MCP registry as io.github.apppainapi/app-pain-api. What users hate about ANY iOS/Android app: clustered complaints, evidence, trends. No key needed. This page covers its hosted endpoint (https://hawkmill.com/mcp).
Is the App Pain API MCP server safe to use?
App Pain API 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 App Pain API MCP server expose?
App Pain API exposes 7 tools: search_apps, mine_app_pain_points, get_pain_trend, get_app_details, get_version_history, and 2 more. Their descriptions and schemas cost roughly 1,231 tokens of context every time the server is loaded.
Does the App Pain API MCP server require authentication?
No. We connected to App Pain API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the App Pain API MCP server still maintained?
App Pain API is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.