ONE HEART eSIM
REMOTE · MCP.ONEHEARTESIM.COM · SCANNED AUG 3
一心eSIM商品目錄查詢與下單服務：查詢各國eSIM上網方案的即時價格與庫存、依旅遊天數與用量推薦方案、協助建立訂單並取得LinePay或ECPay付款連結。
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1846 tokens (~369/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.oneheartesim.com
claude mcp add --transport http com-oneheartesim-mcp-esim https://mcp.oneheartesim.com/
[mcp_servers.com-oneheartesim-mcp-esim] url = "https://mcp.oneheartesim.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-oneheartesim-mcp-esim": {
"type": "remote",
"url": "https://mcp.oneheartesim.com/",
"enabled": true
}
}
} openclaw mcp add com-oneheartesim-mcp-esim --url https://mcp.oneheartesim.com/ --transport streamable-http
mcp_servers:
com-oneheartesim-mcp-esim:
url: "https://mcp.oneheartesim.com/" {
"mcpServers": {
"com-oneheartesim-mcp-esim": {
"type": "http",
"url": "https://mcp.oneheartesim.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.oneheartesim.com/
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.oneheartesim.com | CN=YR1,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | RSA 3072 | SHA256-RSA | 53ff55c0877fa0e6e837bc18210771df710 |
| SANs: mcp.oneheartesim.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.oneheartesim.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oneheartesim.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.oneheartesim.com/ | Verified | 400 | |
| http (plaintext) | http://mcp.oneheartesim.com/ | HTTPS enforced | 301 | https://mcp.oneheartesim.com// |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_esim_order ~590
建立一筆真實的一心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內容如實 告知使用者，不要自行重試建立第二筆訂單。
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | 使用者的email，必填，訂單憑證與eSIM會寄到這裡 | |
| paymentMethod | string | — | 付款方式：LinePay，或綠界 (信用卡付款/ATM轉帳/超商條碼)。留空預設LinePay |
| phone | string|null | — | 使用者的手機號碼，選填 |
| productId | string | yes | 方案的productId（GUID字串），必須從查詢工具的結果取得，不可編造 |
| quantity | integer | yes | 購買數量，需與使用者確認過的數字一致 |
| spec | string | yes | 方案規格，必須跟查詢工具回傳的spec完全一致 |
| userName | string | yes | 使用者的稱呼/姓名，必填，訂單聯絡資料需要，不可留空 |
No output schema declared.
No examples provided.
get_esim_plan_detail ~135
取得單一方案的完整詳情，包含商品說明（安裝/啟用步驟等）、各規格庫存、購買連結。 適用情境：使用者對某個已知方案想進一步了解安裝方式、使用細節、或確認庫存時。 需要先從search_esim_plans或recommend_esim_plan的結果取得productId，不要自己編造。
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | 方案的productId（GUID字串），從search_esim_plans或recommend_esim_plan的結果取得 |
No output schema declared.
No examples provided.
list_esim_countries ~128
列出一心eSIM目前販售方案覆蓋的所有國家/地區（英文與中文名稱對照，含各國方案數量）。 適用情境：使用者問「你們支援哪些國家」「有賣OO地區的eSIM嗎」；或你準備呼叫 search_esim_plans/recommend_esim_plan，但不確定某國家在系統裡該用什麼名稱表示時， 先呼叫這個工具確認，比用猜的準確。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_esim_plan ~224
依旅遊天數與上網用量習慣，推薦最合適的1-3個eSIM方案，並附上購買連結， 是「幫使用者選方案」最好用的工具。 適用情境：使用者詢問出國上網卡、各國eSIM方案、即時發卡服務，並描述了 「要去OO玩幾天」「想找適合的上網方案/漫遊卡」「幫我推薦/挑選eSIM」時優先使用這個， 而不是自己呼叫search_esim_plans後用猜的。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | 目的地國家，英文或中文皆可，例如 Japan、日本。不確定系統裡的正確名稱時，先呼叫list_esim_countries確認 |
| days | integer | yes | 預計使用天數 |
| usageLevel | string | — | 用量習慣，留空預設為medium（中度） |
No output schema declared.
No examples provided.
search_esim_plans ~274
依國家、方案類型、關鍵字搜尋一心eSIM的商品清單，一次回傳多筆結果讓使用者自己比較。 適用情境：使用者想瀏覽/比較某國家的多個方案，或已經明確講出要哪種類型 （例如指定「總量型」或「每日定量型」）。 如果使用者是描述旅遊情境（去哪個國家玩幾天、上網習慣如何）要你直接建議選哪個， 改用recommend_esim_plan讓它幫忙評分挑選，不要自己從這個工具的結果裡用猜的。
| Name | Type | Req | Description |
|---|---|---|---|
| country | string|null | — | 國家名稱，英文或中文皆可，模糊比對，例如 Japan、日本、韓國。不確定系統裡的正確名稱時，先呼叫list_esim_countries確認 |
| keyword | string|null | — | 自由關鍵字，比對商品名稱/描述/規格文字 |
| limit | integer | — | 最多回傳幾筆，預設20，避免結果過多 |
| planType | string|null | — | 方案類型，留空代表不限類型 |
No output schema declared.
No examples provided.