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/ramonclaudio/vexpoWrote 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/ramonclaudio/vexpo/default-expo)<a href="https://agentmods.dev/mcp/ramonclaudio/vexpo/default-expo"><img src="https://agentmods.dev/badge/mcp/ramonclaudio/vexpo/default-expo.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
expo 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 2d 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.
This is a copy
100% identical to expo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"expo": {
"type": "http",
"url": "https://mcp.expo.dev/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.
- 2d ago First seen · 6 lines scan A 68f2b5585e42
expo is an MCP server published in the GitHub repository ramonclaudio/vexpo (6 stars, last pushed 2d 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 is 100% identical to expo, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
better-t-stack
A modern CLI tool for scaffolding end-to-end type-safe TypeScript projects with best practices and customizable configurations. Runs locally from the create-better-t-stack npm package.
rn-devtools-hub
Drive a running React Native or Expo app from inside its JS runtime: see, act, prove. Runs locally from the rn-devtools-hub npm package.
cli
PushToDisplay MCP server — send real-time updates to display boards on iOS and Android devices. Runs locally from the pushtodisplay npm package.
i1n
Agent-complete localization: extract strings, push keys, AI-translate, pull type-safe TS types. Runs locally from the i1n npm package.
mcp-react-native-toolkit
MCP server "mcp-react-native-toolkit" as configured in ItamiForge/mcp-react-native-toolkit. Runs locally from the mcp-react-native-toolkit npm package.
mimi-seed
Mimi Seed MCP server — Firebase + AdMob + Google Play + App Store management for Claude Code / Codex / Cursor / any MCP client. Runs locally from the @yoonion/mimi-seed-mcp npm package.