mcpbeat Sign in

ONE HEART eSIM MCP Server

by oneheartesim-mcp Your server? Claim it
answering

ONE HEART eSIM is answering right now. Last checked 10 min ago. It exposes 5 tools.

一心eSIM商品目錄查詢與下單服務:查詢各國eSIM上網方案的即時價格與庫存、依旅遊天數與用量推薦方案、協助建立訂單並取得LinePay或ECPay付款連結。

Uptime history 91 days of history · worst day 87%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
2951 ms
Response time
average over 24h
open, no key
Access
streamable-http

ONE HEART eSIM missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add esim --transport http https://mcp.oneheartesim.com/
Settings → Connectors → Add custom connector, then paste this address
https://mcp.oneheartesim.com/
~/.codex/config.toml
[mcp_servers.esim]
url = "https://mcp.oneheartesim.com/"
.cursor/mcp.json
{
  "mcpServers": {
    "esim": {
      "url": "https://mcp.oneheartesim.com/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "esim": {
      "type": "http",
      "url": "https://mcp.oneheartesim.com/"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

esim
create_esim_order
建立一筆真實的一心eSIM訂單,並取得真實的付款連結(LinePay或ECPay綠界,二擇一)。 這是會實際寫入正式訂單、串真實金流的動作,不是模擬或試算。 呼叫前必須先完成: 1. 已用search_esim_plans/recommend_esim_plan/get_esim_plan_detail取得正確的productId、 spec,不要自己編造或憑記憶帶入。 2. 已把商品名稱、規格、數量、單價與總金額,跟使用者逐一覆誦確認過,並取得使用者明確 同意下單(不能因為使用者說「好」「幫我訂」等籠統回應就自行猜數量或規格)。 3. 已取得使用者的email與稱呼/姓名(兩者都必填:email用於辨識訂單歸屬與寄送購買憑證/ eSIM QR碼;姓名是訂單聯絡資料的必要欄位,不能留空或代填)。手機可選填。 4. 已詢問使用者想用LinePay還是ECPay綠界付款(留空預設LinePay,但有得選的情況下應該 主動問,不要自己幫使用者決定)。 回傳的paymentUrl要完整、原樣提供給使用者(不要摘要或改寫),並提醒使用者付款完成前 訂單不會出貨。若ok=false,訂單可能已建立但取得付款連結失敗,要把error/note內容如實 告知使用者,不要自行重試建立第二筆訂單。
get_esim_plan_detail
取得單一方案的完整詳情,包含商品說明(安裝/啟用步驟等)、各規格庫存、購買連結。 適用情境:使用者對某個已知方案想進一步了解安裝方式、使用細節、或確認庫存時。 需要先從search_esim_plans或recommend_esim_plan的結果取得productId,不要自己編造。
list_esim_countries
列出一心eSIM目前販售方案覆蓋的所有國家/地區(英文與中文名稱對照,含各國方案數量)。 適用情境:使用者問「你們支援哪些國家」「有賣OO地區的eSIM嗎」;或你準備呼叫 search_esim_plans/recommend_esim_plan,但不確定某國家在系統裡該用什麼名稱表示時, 先呼叫這個工具確認,比用猜的準確。
search_esim_plans
依國家、方案類型、關鍵字搜尋一心eSIM的商品清單,一次回傳多筆結果讓使用者自己比較。 適用情境:使用者想瀏覽/比較某國家的多個方案,或已經明確講出要哪種類型 (例如指定「總量型」或「每日定量型」)。 如果使用者是描述旅遊情境(去哪個國家玩幾天、上網習慣如何)要你直接建議選哪個, 改用recommend_esim_plan讓它幫忙評分挑選,不要自己從這個工具的結果裡用猜的。
recommend
recommend_esim_plan
依旅遊天數與上網用量習慣,推薦最合適的1-3個eSIM方案,並附上購買連結, 是「幫使用者選方案」最好用的工具。 適用情境:使用者詢問出國上網卡、各國eSIM方案、即時發卡服務,並描述了 「要去OO玩幾天」「想找適合的上網方案/漫遊卡」「幫我推薦/挑選eSIM」時優先使用這個, 而不是自己呼叫search_esim_plans後用猜的。

Endpoints

URLTransportStateLatencyChecked
https://mcp.oneheartesim.com/ streamable-http answering 2928 ms 10 min ago

ONE HEART eSIM — questions

Answers built from our own checks of this server.

What can ONE HEART eSIM do?
It exposes 5 tools, read directly from the server on our last check. Among them: create_esim_order, get_esim_plan_detail, list_esim_countries, recommend_esim_plan, search_esim_plans. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ONE HEART eSIM working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 2951 ms. The bar chart above shows every period we have measured.
How do I connect ONE HEART eSIM?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ONE HEART eSIM need an API key?
No. ONE HEART eSIM completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.