ONE HEART eSIM
com.oneheartesim.mcp/esim · 1.0.0
一心eSIM商品目錄查詢與下單服務:查詢各國eSIM上網方案的即時價格與庫存、依旅遊天數與用量推薦方案、協助建立訂單並取得LinePay或ECPay付款連結。
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 35 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.oneheartesim.com/streamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- OneHeart-eSIM.Mcp 1.0.0.0
- Handshake time
- 2372 ms
- HTTP status
- 200
The tools it lists (5, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
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內容如實 告知使用者,不要自行重試建立第二筆訂單。
recommend_esim_plan依旅遊天數與上網用量習慣,推薦最合適的1-3個eSIM方案,並附上購買連結, 是「幫使用者選方案」最好用的工具。 適用情境:使用者詢問出國上網卡、各國eSIM方案、即時發卡服務,並描述了 「要去OO玩幾天」「想找適合的上網方案/漫遊卡」「幫我推薦/挑選eSIM」時優先使用這個, 而不是自己呼叫search_esim_plans後用猜的。
list_esim_countries列出一心eSIM目前販售方案覆蓋的所有國家/地區(英文與中文名稱對照,含各國方案數量)。 適用情境:使用者問「你們支援哪些國家」「有賣OO地區的eSIM嗎」;或你準備呼叫 search_esim_plans/recommend_esim_plan,但不確定某國家在系統裡該用什麼名稱表示時, 先呼叫這個工具確認,比用猜的準確。
search_esim_plans依國家、方案類型、關鍵字搜尋一心eSIM的商品清單,一次回傳多筆結果讓使用者自己比較。 適用情境:使用者想瀏覽/比較某國家的多個方案,或已經明確講出要哪種類型 (例如指定「總量型」或「每日定量型」)。 如果使用者是描述旅遊情境(去哪個國家玩幾天、上網習慣如何)要你直接建議選哪個, 改用recommend_esim_plan讓它幫忙評分挑選,不要自己從這個工具的結果裡用猜的。
get_esim_plan_detail取得單一方案的完整詳情,包含商品說明(安裝/啟用步驟等)、各規格庫存、購買連結。 適用情境:使用者對某個已知方案想進一步了解安裝方式、使用細節、或確認庫存時。 需要先從search_esim_plans或recommend_esim_plan的結果取得productId,不要自己編造。
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.oneheartesim.mcp/esim, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 75 days ago. The registry entry