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/kangih90/hungry-esim-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/kangih90/hungry-esim-mcp/esim)<a href="https://agentmods.dev/mcp/kangih90/hungry-esim-mcp/esim"><img src="https://agentmods.dev/badge/mcp/kangih90/hungry-esim-mcp/esim/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/kangih90/hungry-esim-mcp/esim"><img src="https://agentmods.dev/badge/mcp/kangih90/hungry-esim-mcp/esim.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
esim 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 10d 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
{
"esim": {
"url": "https://api.hungry-esim.com/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.
- 10d ago First seen · 6 lines scan A e2a5a1dde8a8
esim is an MCP server published in the GitHub repository kangih90/hungry-esim-mcp (0 stars, last pushed 23d 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-server
Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral. Runs locally from the @roamzy/mcp-server npm package. Needs 3 environment variables to run.
goodbarber
MCP server "goodbarber", hosted remotely at mcp.goodbarber.dev, as configured in goodbarber/goodbarber-skills.
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.
appstore-flow
App Store Connect from your terminal — manage iOS listings, IAPs, subscriptions, and screenshots from YAML files. CLI + bundled MCP server. Runs locally from the appstore-flow npm package.
mcp-esim
Travel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key. Runs locally from the @worldcitisim/mcp-esim npm package.
app-store-connect
App Store Connect MCP server — manage iOS/macOS apps, TestFlight, in-app subscriptions, and App Store metadata from Cursor, Claude, or any Model Context Protocol client. Uses official App Store Connect API. Runs locally from the mcp-asc npm package. Needs 4 environment variables to run.