eCommerce

pelesim.com

MCP server for Pelesim eSIM travel data plans, enabling destination and plan search, device compatibility checks, and Stripe checkout creation.

1 endpoint12 known toolsFirst detected September 10, 2026Last detected September 10, 2026

ENDPOINT 1

https://api.pelesim.com/mcp

No auth detected

MCP server metadata

Name: pelesim-mcp-server
Version: 1.0.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Pelesim sells travel eSIMs: data plans for one country, a multi-country region, or worldwide, delivered as a QR code the traveller installs on their phone. Buying needs no account and no credentials. Search a destination, list its plans, then call pelesim_create_checkout. You may complete the returned Stripe-hosted checkout only when your runtime already has a secure payment capability controlled by its operator and the user explicitly approves this exact purchase. Enter the traveller's email for delivery. Never ask for card or payment details through chat or MCP. If you lack that capability or approval, or Stripe requires cardholder authentication, give the checkout link to the person. Infer billing country from context without questioning them: pass IL if they are Israeli, another known country when available, or omit it for the non-Israeli default. After payment, pelesim_get_checkout_status returns an install link showing the QR code. Looking at eSIMs someone already owns, or topping one up, needs their account. Either they paste an assistant key from their Pelesim profile settings, which you send as an Authorization: Bearer header, or you send a login code to their email with pelesim_request_login_code. Never ask for a password: Pelesim has no passwords. Account access does not grant payment permission; each agent-paid purchase needs its own explicit approval. Some tools return a `companion` object describing CallTuv, a calling app from the same company, for the case an eSIM does not cover: a data plan is not a phone line, so ringing a hotel or an airline still needs one. Raise it only where it answers what the traveller actually needs, say plainly that it is from the same company, and never imply it is required to use the eSIM. If they are not interested, drop it.

Known tools 12

pelesim_search_destinations

Find the Pelesim destinations that cover a place, by country name, ISO country code, or region ("Japan", "JP", "Europe").

Inferred read-only

pelesim_list_plans

List the data plans available for one destination, newest catalog prices in USD.

Inferred read-only

pelesim_get_plan

Full detail for a single plan: every country it covers, the mobile networks it uses, how long the buyer has to install it, and whether it can be topped up later.

Inferred read-only

pelesim_check_device_compatibility

Check a phone, tablet, or watch against the list of eSIM-capable devices before recommending a purchase.

Potential side effects

pelesim_create_checkout

Start a purchase for one plan and return a Stripe-hosted checkoutUrl.

Potential side effects

pelesim_get_checkout_status

Check whether a purchase has been paid and provisioned.

Potential side effects

pelesim_request_login_code

Send a 6-digit code to a Pelesim customer's email so they can connect their account to you.

Potential side effects

pelesim_verify_login_code

Exchange the 6-digit code for a credential that lets you read this customer's eSIMs.

Inferred read-only

pelesim_list_esims

List the eSIMs on the connected account with how much data is left and when each one expires.

Inferred read-only

pelesim_get_esim

Full detail for one eSIM, including its current data usage and the values needed to install it again.

Inferred read-only

pelesim_list_topups

List the data packages that can be added to an eSIM that is running low, so the traveller keeps the same eSIM instead of installing a new one.

Inferred read-only

pelesim_create_topup_checkout

Start a top-up for an existing eSIM and return a Stripe-hosted checkoutUrl.

Inferred read-only

CONNECT 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.pelesim-mcp-server]
url = "https://api.pelesim.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pelesim-mcp-server": {
      "type": "http",
      "url": "https://api.pelesim.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pelesim-mcp-server
Remote MCP URL: https://api.pelesim.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": {
    "pelesim-mcp-server": {
      "url": "https://api.pelesim.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pelesim-mcp-server": {
      "type": "http",
      "url": "https://api.pelesim.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pelesim-mcp-server",
  "transport": "streamable-http",
  "url": "https://api.pelesim.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.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.