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/concavegit/app-store-connect-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/concavegit/app-store-connect-mcp-server/appstore-connect-mcp-server)<a href="https://agentmods.dev/mcp/concavegit/app-store-connect-mcp-server/appstore-connect-mcp-server"><img src="https://agentmods.dev/badge/mcp/concavegit/app-store-connect-mcp-server/appstore-connect-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
appstore-connect-mcp-server 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 7d 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
{ "appstore-connect-mcp-server": { "command": "npx", "args": [ "-y", "appstore-connect-mcp-server" ] } }
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.
- 7d ago First seen · 9 lines scan A 4d3fb6185ee8
appstore-connect-mcp-server is an MCP server published in the GitHub repository concavegit/app-store-connect-mcp-server (0 stars, last pushed 1mo 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. It comes from a forked repository.
Other mcp servers, from other repositories
xcodebuildmcp
XcodeBuildMCP is a Model Context Protocol server that provides tools for Xcode project management, simulator management, and app utilities. Runs locally from the xcodebuildmcp npm package. Needs 1 environment variable to run.
android-sqlite-mcp
A Model Context Protocol (MCP) server to connect AI agents directly to the embedded SQLite/Room databases of your Android applications. Runs locally from the android-sqlite-mcp npm package.
expo-local-docs-mcp
MCP server for Expo documentation - reads local .mdx files for blazing fast performance. Works out of the box with zero configuration. Runs locally from the expo-local-docs-mcp npm package.
mobile-builder-mcp
MCP server "mobile-builder-mcp" as configured in daffy0208/ai-dev-standards. Runs C:\Users\david\OneDrive - Qolcom\AI\AI_Development_Projects\ai-dev-standards\MCP-SERVERS\mobile-builder-mcp\dist\index.js with node.
ulink
Deep linking for iOS, Android & Flutter. Firebase Dynamic Links alternative. Runs locally from the @ulinkly/mcp-server npm package. Needs 1 environment variable to run.
mcp-connect
MCP server for iOS Simulator control and browser automation - unified toolkit for mobile and web testing. Runs locally from the @plaintest/mcp-connect npm package.