一心漫遊 ONE HEART eSIM MCP server

• Registry namecom.oneheartesim.mcp/esimverified in the MCP registry

The registry name sits under oneheartesim.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools5
• Server calls itselfOneHeart-eSIM.Mcp
• Server version1.0.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 2698 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer3670 ms
• Space in an agent's context≈ 808 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 5 of 5

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• create_esim_order

  建立一筆真實的一心eSIM訂單，並取得真實的付款連結（LinePay或ECPay綠界，二擇一）。 這是會實際寫入正式訂單、串真實金流的動作，不是模擬或試算。 呼叫前必須先完成： 1. 已用search_esim_plans/recommend_esim_plan/get_esim_plan_detail取得正確的productId、 spec，不要自己編造或憑記憶帶入。 2. 已把商品名稱、規格、數量、單價與總金額，跟使用者逐一覆誦確認過，並取得使用者明確…

• 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，不要自己編造。