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/ophydami/storeboard-mcpWrote 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/ophydami/storeboard-mcp/storeboard)<a href="https://agentmods.dev/mcp/ophydami/storeboard-mcp/storeboard"><img src="https://agentmods.dev/badge/mcp/ophydami/storeboard-mcp/storeboard/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/ophydami/storeboard-mcp/storeboard"><img src="https://agentmods.dev/badge/mcp/ophydami/storeboard-mcp/storeboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
storeboard 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 8d 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
{
"storeboard": {
"url": "https://storeboard.dev/api/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.
- 8d ago First seen · 6 lines scan A 5ad89c4cb5fd
storeboard is an MCP server published in the GitHub repository ophydami/storeboard-mcp (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. 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
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.
xcodebuildmcp-dev
MCP server "xcodebuildmcp-dev" as configured in getsentry/XcodeBuildMCP. Runs ../../build/cli.js with node. Needs 4 environment variables to run.
XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. Runs locally from the xcodebuildmcp npm package. Needs 4 environment variables to run.
asc-mcp
Every App Store Connect + StoreKit 2 endpoint. 890 tools in 13 profiles, narrow to 27. Runs locally from the @erayendes/asc-mcp npm package. Needs 5 environment variables to run.
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.