Appfollow
Server Details
AppFollow MCP — App Store & Google Play reviews, ratings, and ASO keyword
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.2% over 22 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-appfollow
- GitHub Stars
- 0
- Server Listing
- mcp-appfollow
TDQS
Scored across 39 tools
Several tools have genuinely redundant or near-identical purposes: ask_pipeworx, ask_pipeworx_beta (which text says currently matches ask_pipeworx exactly), ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve as overlapping entry points to the same data router. Similarly, ai_visibility_check vs scan_competitor_ai_presence and the polymarket_edges/arbitrage/fill_risk/kalshi_spread cluster make it hard for an agent to pick the right tool without reading very long descriptions.
Naming is mixed but readable: some tools use verb_noun (list_subscriptions, resolve_entity, validate_claim, scan_dependency), some use domain prefixes (appfollow_*, polymarket_*, ask_pipeworx_*, pipeworx_*), and others are bare noun phrases (entity_profile, company_facts, bet_research, kalshi_weather_edge). All names are snake_case and mostly descriptive, but there is no single predictable convention across the set.
39 tools is excessive for a server ostensibly named 'Appfollow' but actually covering app-store analytics, general structured data lookup, prediction-market arbitrage, memory, subscriptions, npm scanning, and AI-presence checks. The tool count is well above the 25+ threshold and the scope feels like multiple distinct products bundled together rather than one coherent surface.
For its broad self-appointed domain, the surface is fairly complete: the data-research side has entry points, grounding, entity resolution, profiles, comparisons, change feeds, claim validation, and in-record search; the prediction-market side covers edge discovery, persistence tracking, fill-risk, cross-venue spreads, and resolution auditing. Minor gaps exist — e.g., no app-level metadata tool for the AppFollow portion and no simple 'get app info' — but these are workable dead ends rather than blocking failures.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
22 tool updates
- Changed
ai_visibility_check1 field changed- added
Input schema / examplesAdded value: +[ + { + "entity": "Tesla" + } +]
- Changed
ask_pipeworx_beta1 field changed- added
Input schema / examplesAdded value: +[ + { + "question": "What is the current US unemployment rate?" + } +]
- Changed
ask_pipeworx_grounded1 field changed- added
Input schema / examplesAdded value: +[ + { + "question": "What was Apple's fiscal 2023 revenue?" + } +]
- Changed
company_facts4 fields changed- added
Input schema / examplesAdded value: +[ + { + "attribute": "revenue", + "company": "AAPL", + "period": { + "fiscal_year": 2023, + "type": "annual" + } + } +] - added
Input schema / properties / as_ofAdded value: +{ + "description": "Past ISO timestamp with timezone. Replay the latest answer actually recorded by that instant; no invented history or live fallback.", + "type": "string" +} - added
Input schema / properties / freshnessAdded value: +{ + "description": "cached (default) permits an eligible stored answer; fresh requires an upstream refresh and never silently falls back to stale data.", + "enum": [ + "cached", + "fresh" + ], + "type": "string" +} - added
Input schema / properties / max_ageAdded value: +{ + "description": "Maximum age in seconds of the upstream publication, not our fetch. Older or undated facts are withheld.", + "maximum": 3155760000, + "minimum": 0, + "type": "number" +}
- Changed
compare_entities1 field changed- added
Input schema / examplesAdded value: +[ + { + "type": "company", + "values": [ + "AAPL", + "MSFT" + ] + } +]
- Changed
deep_research1 field changed- added
Input schema / examplesAdded value: +[ + { + "depth": "quick", + "question": "What is the current US unemployment rate and how has it changed over the past year?" + } +]
- Changed
entity_profile1 field changed- added
Input schema / examplesAdded value: +[ + { + "type": "company", + "value": "AAPL" + } +]
- Changed
generate_llms_txt1 field changed- added
Input schema / examplesAdded value: +[ + { + "url": "https://pipeworx.io" + } +]
- Changed
pipeworx_feedback1 field changed- added
Input schema / examplesAdded value: +[ + { + "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.", + "type": "other" + } +]
- Changed
pipeworx_trending1 field changed- added
Input schema / examplesAdded value: +[ + { + "window": "7d" + } +]
- Changed
polymarket_arbitrage1 field changed- added
Input schema / examplesAdded value: +[ + { + "topic": "Fed rate decision" + } +]
- Changed
polymarket_edge_tracker1 field changed- added
Input schema / examplesAdded value: +[ + { + "days": 14, + "window": "1wk" + } +]
- Changed
polymarket_edges3 fields changed- added
Input schema / examplesAdded value: +[ + { + "limit": 5, + "window": "1wk" + } +] - changed
Input schema / properties / min_edge_pp / descriptionPrevious value: -"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee." - changed
Input schema / properties / slippage_pp / descriptionPrevious value: -"Assumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model."New value: +"Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw |edge| before ranking and Kelly sizing, ON TOP OF Polymarket's own taker fee — which is NOT zero (rate 0.04-0.07 depending on category, read off each market's own published fee schedule; see fees_pp_applied on every row and fees.ts for the full schedule). Bump slippage for very thin partitions; drop to 0 if you have a smarter fill model — the fee still applies regardless."
- Changed
polymarket_fill_risk1 field changed- added
Input schema / examplesAdded value: +[ + { + "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636", + "side": "buy_yes", + "size_usd": 1000 + } +]
- Changed
recent_changes1 field changed- added
Input schema / examplesAdded value: +[ + { + "since": "30d", + "type": "company", + "value": "AAPL" + } +]
- Changed
remember1 field changed- added
Input schema / examplesAdded value: +[ + { + "key": "target_ticker", + "value": "AAPL" + } +]
- Changed
resolve_entity1 field changed- added
Input schema / examplesAdded value: +[ + { + "type": "company", + "value": "AAPL" + } +]
- Changed
scan_competitor_ai_presence1 field changed- added
Input schema / examplesAdded value: +[ + { + "entities": [ + "Pipeworx", + "Zapier" + ] + } +]
- Changed
scan_dependency1 field changed- added
Input schema / examplesAdded value: +[ + { + "package": "left-pad" + } +]
- Changed
search_within1 field changed- added
Input schema / examplesAdded value: +[ + { + "query": "supply-chain risk", + "text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter." + } +]
- Changed
suggest_questions1 field changed- added
Input schema / examplesAdded value: +[ + { + "topic": "finance" + } +]
- Changed
validate_claim1 field changed- added
Input schema / examplesAdded value: +[ + { + "claim": "Apple's fiscal 2023 revenue was $383 billion" + } +]
39 tool updates
- First observed
ai_visibility_check - First observed
appfollow_aso_keywords - First observed
appfollow_ratings - First observed
appfollow_reviews - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
company_facts - First observed
compare_entities - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
App Store & Google Play keyword ranks, rivals, reviews, charts and AI visibility as an MCP server
Track your apps' keyword rankings, reviews and store listings on App Store, Google Play and more.
App Store keyword rankings, competitors, markets, reviews and analytics for iOS apps, from your AI.
App Store keyword research, rank tracking and App Store Connect performance for your iOS apps.
Related MCP Servers
- AlicenseBqualityAmaintenanceUnified MCP server for App Store Connect & Google Play Console — manage listings, screenshots, releases, reviews & submissions9162 npm35MIT
- AlicenseNot gradedqualityBmaintenanceProvides live App Store and Google Play data as MCP tools, enabling search, app details, reviews, charts, estimates, and more through natural language.1MIT
- FlicenseNot gradedqualityBmaintenanceProvides MCP tools to search and retrieve Apple App Store and Google Play app data, including app details, reviews, charts, developer info, and ASO keyword/rank estimates.-
- AlicenseNot gradedqualityBmaintenanceMCP server for managing App Store Optimization: add apps, track keywords, pull health reports, spy on competitors, find keyword opportunities, and write AI copy suggestions.6MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.