Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/trendsapi-ai/app-store-trends-api/app-storegit clone --depth 1 https://github.com/trendsapi-ai/app-store-trends-apiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/trendsapi-ai/app-store-trends-api/app-store)<a href="https://agentmods.dev/mcp/trendsapi-ai/app-store-trends-api/app-store"><img src="https://agentmods.dev/badge/mcp/trendsapi-ai/app-store-trends-api/app-store.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
app-store scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- app-store — 86% identical, 2 lines differ
What it actually says
{ "app-store": { "url": "https://app-store.api.trendsapi.ai/mcp", "type": "streamable-http" } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 6 lines scan A 80360cf10e4d
app-store is an MCP server published in the GitHub repository trendsapi-ai/app-store-trends-api (0 stars, last pushed 17d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp
Access your app analytics, ASO tools, and app market intelligence with Appfigures. Runs locally from the @appfigures/cli npm package. Needs 1 environment variable to run.
storepilot-mcp
StorePilot — one MCP server to run your entire app portfolio across Google Play and the App Store. Runs locally from the storepilot Python package. Needs 6 environment variables to run.
store-preflight-mcp
App Store / Play rejection preflight for agents — maps API usage to the declaration it obliges, before the binary is rejected. Runs locally from the store-preflight-mcp Python package.
app-publisher-mcp
MCP server for vibe coders - AI app icon generation, auto-resizing for iOS/Android, and store publishing automation. Runs locally from the @seungmanchoi/app-publisher-mcp npm package.
compose-hot-reload
MCP server "compose-hot-reload" as configured in meshtastic/Meshtastic-Android. Launched with ./gradlew --no-daemon --quiet --console=plain :desktopApp:hotMcpServer.
app-publish
MCP server for App Store Connect & Google Play Console — iOS/Android app management. Runs locally from the app-publish-mcp npm package. Needs 4 environment variables to run.