eCommerce
sinoconnection.com
Provides search, details, compatibility checks, checkout, and support for travel eSIM plans.
ENDPOINT 1
https://mcp.sinoconnection.com/mcp
MCP server metadata
- Name
- sinoconnection-esim
- Version
- 1.0.0
Known tools 5
get_plan_detailsFull details for a specific plan by id — call this WHENEVER the customer selects or shows interest in a plan; do NOT just quote a bare price.
Inferred read-onlycheck_device_compatibilityCheck whether a phone/tablet model supports eSIM before recommending a plan.
Inferred read-onlyget_helpAnswer customer support and policy questions about SinoConnection eSIMs: the REFUND POLICY, how to INSTALL (with step-by-step videos), activation, HOW THE NO-VPN CHINA ACCESS WORKS (roaming / exit IP — see faq.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sinoconnection-esim]
url = "https://mcp.sinoconnection.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sinoconnection-esim": {
"type": "http",
"url": "https://mcp.sinoconnection.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sinoconnection-esim
Remote MCP URL: https://mcp.sinoconnection.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sinoconnection-esim": {
"url": "https://mcp.sinoconnection.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sinoconnection-esim": {
"type": "http",
"url": "https://mcp.sinoconnection.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sinoconnection-esim",
"transport": "streamable-http",
"url": "https://mcp.sinoconnection.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.