# Slashtel (remote · slashtel.com)

Travel data eSIMs in about 200 destinations and mobile top-ups in 100+ countries, live prices.

- Trust score: 78/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-08

## Components

- remote · `slashtel.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-slashtel-slashtel/api-mcp.md), [page](https://verifymcp.io/servers/com-slashtel-slashtel/api-mcp)

## Channel facts

- Endpoint: `https://slashtel.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-08.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 613 tokens (~153/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Slashtel MCP server?

Slashtel is a hosted endpoint at https://slashtel.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-slashtel-slashtel 'https://slashtel.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-slashtel-slashtel": {
      "url": "https://slashtel.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-slashtel-slashtel": {
      "type": "http",
      "url": "https://slashtel.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-slashtel-slashtel]
url = "https://slashtel.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-slashtel-slashtel": {
      "type": "remote",
      "url": "https://slashtel.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-slashtel-slashtel --url 'https://slashtel.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-slashtel-slashtel:
    url: "https://slashtel.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-slashtel-slashtel": {
      "Transport": "http",
      "Url": "https://slashtel.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-slashtel-slashtel -t streamable-http -u 'https://slashtel.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-slashtel-slashtel": {
      "type": "http",
      "url": "https://slashtel.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-08 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-06 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-29 (score 74, +1)

- [security] Tool “get_topup_plans” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-09-28 (score 73)

First indexed and scored.

## MCP tools (4)

### `list_esim_destinations` (~71 tokens)

List eSIM destinations

Countries and regions Slashtel sells travel eSIMs for, with the lowest live price (USD) and number of plans. Optional search text filters by name.

Input parameters:

- `search` (string): Part of a country or region name, e.g. 'turk' or 'europe'

### `get_esim_plans` (~113 tokens)

Get eSIM plans

Live travel eSIM plans for one destination: data (GB), validity (days), price (USD) and price per GB. Use an ISO-2 country code (e.g. TR, JP, US, GB) or a destination code from list_esim_destinations. Optional filters narrow the list.

Input parameters:

- `destination` (string, required): ISO-2 country code or destination code
- `min_days` (number): Minimum validity in days
- `min_gb` (number): Minimum data in GB

### `get_topup_plans` (~76 tokens)

Get mobile top-up options

Detects the operator of a mobile number and returns the live top-up options for it: what the recipient receives, validity where it applies, and the price in USD. The number must include the country code, e.g. +911234567890.

Input parameters:

- `phone` (string, required): Full international mobile number with country code

### `create_checkout_link` (~153 tokens)

Create checkout link

Returns a slashtel.com link with the chosen eSIM plan or top-up already selected. Share it with the user: they enter their email and pay on the site. For type 'esim' pass plan_id. For type 'topup' pass phone, operator_code and send_value from get_topup_plans.

Input parameters:

- `operator_code` (string): Top-up: operator_code from get_topup_plans
- `phone` (string): Top-up: the full international number
- `plan_id` (string): eSIM plan_id from get_esim_plans
- `send_value` (number): Top-up: send_value from get_topup_plans
- `type` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-slashtel-slashtel/api-mcp#diagnostics

## Score history

- 2026-10-08: 78
- 2026-10-06: 77
- 2026-10-04: 76
- 2026-10-03: 75
- 2026-10-02: 75
- 2026-10-01: 74
- 2026-09-30: 74
- 2026-09-29: 74
- 2026-09-28: 73

## Common questions

### What is the Slashtel MCP server?

Slashtel is an MCP server listed in the public MCP registry as com.slashtel/slashtel. Travel data eSIMs in about 200 destinations and mobile top-ups in 100+ countries, live prices. This page covers its hosted endpoint (https://slashtel.com/api/mcp).

### Is the Slashtel MCP server safe to use?

Slashtel scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Slashtel MCP server expose?

Slashtel exposes 4 tools: list_esim_destinations, get_esim_plans, get_topup_plans, create_checkout_link. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.

### Does the Slashtel MCP server require authentication?

No. We connected to Slashtel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Slashtel MCP server still maintained?

Slashtel is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://slashtel.com/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-slashtel-slashtel/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-slashtel-slashtel/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-slashtel-slashtel/api-mcp