ONE HEART eSIM MCP server
com.oneheartesim.mcp/esimmcp.oneheartesim.comstreamable-httpv1.0.0Scanned
一心eSIM商品目錄查詢與下單服務:查詢各國eSIM上網方案的即時價格與庫存、依旅遊天數與用量推薦方案、協助建立訂單並取得LinePay或ECPay付款連結。
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ONE HEART eSIM MCP server can do
The ONE HEART eSIM MCP server is published by mcp.oneheartesim.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: create_esim_order and recommend_esim_plan), but cannot delete data. 3 tools only read.
1 tool can send data out of your system (create_esim_order).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
create_esim_order建立一筆真實的一心eSIM訂單,並取得真實的付款連結(LinePay或ECPay綠界,二擇一)。 這是會實際寫入正式訂單、串真實金流的動作,不是模擬或試算。 呼叫前必須先完成: 1.Can send data outNo findings
Why it is in this group
- The name "create_esim_order" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it 建立一筆真實的一心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後用猜的。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 依旅遊天數與上網用量習慣,推薦最合適的1-3個eSIM方案,並附上購買連結, 是「幫使用者選方案」最好用的工具。 適用情境:使用者詢問出國上網卡、各國eSIM方案、即時發卡服務,並描述了 「要去OO玩幾天」「想找適合的上網方案/漫遊卡」「幫我推薦/挑選eSIM」時優先使用這個, 而不是自己呼叫search_esim_plans後用猜的。
Only reads 3Show 3 read-only tools
get_esim_plan_detail取得單一方案的完整詳情,包含商品說明(安裝/啟用步驟等)、各規格庫存、購買連結。 適用情境:使用者對某個已知方案想進一步了解安裝方式、使用細節、或確認庫存時。 需要先從search_esim_plans或recommend_esim_plan的結果取得productId,不要自己編造。No findings
Why it is in this group
- The name "get_esim_plan_detail" says "get": a word for reading.
Description, as the server wrote it 取得單一方案的完整詳情,包含商品說明(安裝/啟用步驟等)、各規格庫存、購買連結。 適用情境:使用者對某個已知方案想進一步了解安裝方式、使用細節、或確認庫存時。 需要先從search_esim_plans或recommend_esim_plan的結果取得productId,不要自己編造。
list_esim_countries列出一心eSIM目前販售方案覆蓋的所有國家/地區(英文與中文名稱對照,含各國方案數量)。 適用情境:使用者問「你們支援哪些國家」「有賣OO地區的eSIM嗎」;或你準備呼叫 search_esim_plans/recommend_esim_plan,但不確定某國家在系統裡該用什麼名稱表示時, 先呼叫這個工具確認,比用猜的準確。No findings
Why it is in this group
- The name "list_esim_countries" says "list": a word for reading.
Description, as the server wrote it 列出一心eSIM目前販售方案覆蓋的所有國家/地區(英文與中文名稱對照,含各國方案數量)。 適用情境:使用者問「你們支援哪些國家」「有賣OO地區的eSIM嗎」;或你準備呼叫 search_esim_plans/recommend_esim_plan,但不確定某國家在系統裡該用什麼名稱表示時, 先呼叫這個工具確認,比用猜的準確。
search_esim_plans依國家、方案類型、關鍵字搜尋一心eSIM的商品清單,一次回傳多筆結果讓使用者自己比較。 適用情境:使用者想瀏覽/比較某國家的多個方案,或已經明確講出要哪種類型 (例如指定「總量型」或「每日定量型」)。 如果使用者是描述旅遊情境(去哪個國家玩幾天、上網習慣如何)要你直接建議選哪個, 改用recommend_esim_plan讓它幫忙評分挑選,不要自己從這個工具…No findings
Why it is in this group
- The name "search_esim_plans" says "search": a word for reading.
Description, as the server wrote it 依國家、方案類型、關鍵字搜尋一心eSIM的商品清單,一次回傳多筆結果讓使用者自己比較。 適用情境:使用者想瀏覽/比較某國家的多個方案,或已經明確講出要哪種類型 (例如指定「總量型」或「每日定量型」)。 如果使用者是描述旅遊情境(去哪個國家玩幾天、上網習慣如何)要你直接建議選哪個, 改用recommend_esim_plan讓它幫忙評分挑選,不要自己從這個工具的結果裡用猜的。
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.oneheartesim.com/: tools/list returned 5 tools to an anonymous client, including create_esim_order (write), recommend_esim_plan (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http esim https://mcp.oneheartesim.com/claude mcp add --transport http esim https://mcp.oneheartesim.com/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__esim__list_esim_countries",
"mcp__esim__search_esim_plans",
"mcp__esim__get_esim_plan_detail"
],
"ask": [
"mcp__esim__create_esim_order",
"mcp__esim__recommend_esim_plan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as esim. Review it before you use it.
Capability tags behind 1 rule
- mcp__esim__create_esim_order outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.oneheartesim.mcp/esim/verify?hash=99c29c9ab57b353787053e5a96fb6fa0aaeb05ef675015a5006728bd628e1725" | jq -e '.changed == false'Pinned hash 99c29c9ab57b, from Nov 13, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.oneheartesim.mcp/esim/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.oneheartesim.mcp/esim)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
ONE HEART eSIM MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ONE HEART eSIM MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ONE HEART eSIM MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ONE HEART eSIM MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ONE HEART eSIM MCP server have?
- 5 tools: 2 write, 3 read. create_esim_order, recommend_esim_plan, list_esim_countries, search_esim_plans and get_esim_plan_detail.
Does the ONE HEART eSIM MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ONE HEART eSIM MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_esim_order.
Has the ONE HEART eSIM MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.