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.
git clone --depth 1 https://github.com/applyra-io/mcp-serverWrote 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/applyra-io/mcp-server/applyra)<a href="https://agentmods.dev/mcp/applyra-io/mcp-server/applyra"><img src="https://agentmods.dev/badge/mcp/applyra-io/mcp-server/applyra/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/applyra-io/mcp-server/applyra"><img src="https://agentmods.dev/badge/mcp/applyra-io/mcp-server/applyra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
applyra 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 14d 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.
What it actually says
{
"applyra": {
"type": "http",
"url": "https://www.applyra.io/api/mcp"
}
}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.
- 14d ago First seen · 6 lines scan A 91d0550097f7
applyra is an MCP server published in the GitHub repository applyra-io/mcp-server (0 stars, last pushed 10d 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-10-08.
Other mcp servers, from other repositories
storelift
App Store & Google Play keyword ranks, rivals, reviews, charts and AI visibility as an MCP server. Runs locally from the storelift-mcp npm package. Needs 2 environment variables to run.
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.
app-store-operator
Free App Store competitive intelligence for Claude — rival downloads, revenue, and ASO keywords. Runs locally from the app-store-operator npm package. Needs 1 environment variable to run.
asoatlas
MCP server "asoatlas", hosted remotely at asoatlas.com, as configured in asoatlas/mcp.
hidden-aso
MCP server "hidden-aso", hosted remotely at localhost, as configured in Aero25x/ASO-Copilot.
openaso
App Store Optimization for AI agents: keyword ranks, suggestions, popularity, competitors, reviews. Remote server at mcp.openaso.ai.