eCommerce
esimyfi.live
MCP server for eSIM dealer operations that retrieves account balance, lists countries and plans, and creates or lists eSIM orders.
ENDPOINT 1
https://esimyfi.live/mcp
MCP server metadata
- Name
- yfinet-esim
- Version
- 1.0.0
YFi Net eSIM dealer API. Develop with a yf_test_ key: orders are sandboxed (test_mode:true, ICCID 8999…, no charges, no real eSIMs). Flow: get_balance → list_countries → list_plans → create_order → get_order / get_usage → topup / cancel. Use dealer_reference for idempotent order retries. period_num (1-60) only on is_daily plans. Never place live (yf_live_) orders unless the human explicitly asks. Full docs: https://esimyfi.live/llms.txt
Known tools 12
get_balanceGet the dealer account balance, account mode, and whether live ordering is enabled.
Inferred read-onlyget_orderGet one order by its order_id (ord_…): status, ICCID, activation code, plan, charge.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.yfinet-esim]
url = "https://esimyfi.live/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"yfinet-esim": {
"type": "http",
"url": "https://esimyfi.live/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: yfinet-esim
Remote MCP URL: https://esimyfi.live/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"yfinet-esim": {
"url": "https://esimyfi.live/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"yfinet-esim": {
"type": "http",
"url": "https://esimyfi.live/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "yfinet-esim",
"transport": "streamable-http",
"url": "https://esimyfi.live/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.