# SimOptions (remote · www.simoptions.com)

Find and compare travel eSIM plans, check phone eSIM compatibility, and open each plan's page.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.simoptions.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-simoptions-connector/api-connector-2.md), [page](https://verifymcp.io/servers/com-simoptions-connector/api-connector-2)

## Channel facts

- Endpoint: `https://www.simoptions.com/api/connector/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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 522 tokens (~174/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

SimOptions is a hosted endpoint at https://www.simoptions.com/api/connector/, 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-simoptions-connector 'https://www.simoptions.com/api/connector/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-simoptions-connector": {
      "url": "https://www.simoptions.com/api/connector/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-simoptions-connector": {
      "type": "http",
      "url": "https://www.simoptions.com/api/connector/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-simoptions-connector]
url = "https://www.simoptions.com/api/connector/"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-simoptions-connector:
    url: "https://www.simoptions.com/api/connector/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-simoptions-connector": {
      "Transport": "http",
      "Url": "https://www.simoptions.com/api/connector/"
    }
  }
}
```

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-simoptions-connector": {
      "type": "http",
      "url": "https://www.simoptions.com/api/connector/"
    }
  }
}
```

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-11-21 (score 74, +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-11-19 (score 73, +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.

### 2026-11-18 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 72)

First indexed and scored.

## MCP tools (3)

### `destinations_search` (~125 tokens)

Search destinations

Find the destinations SimOptions sells travel eSIMs for, by country or region name in any language, or by code. Returns up to 10 destinations, best match first: each one's code (pass it to plans_find), name, type (country or region), the countries it covers and its page on simoptions.com. A country with no page of its own is answered with the regional plans that cover it.

Input parameters:

- `query` (string, required): Country or region name in any language, or its code: "Japan", "Europe", "JP". At least 2 characters.

### `plans_find` (~263 tokens)

Find eSIM plans

List the SimOptions travel eSIM plans in stock for a trip. With one destination code: the plans its page on simoptions.com lists. With several: the plans that cover every one of them. Destination codes come from destinations_search. Optional filters: shortest validity, least data (unlimited plans always qualify), unlimited data only. Cheapest first, at most 20; total says how many matched. Each plan carries its id (EAN), validity, data, networks per country, 5G, calls, SMS, phone number, whether it can be topped up, operator, price in the asked currency, and its page on simoptions.com, where it is bought.

Input parameters:

- `currency` (string): ISO 4217 code of the currency the prices are in, e.g. "USD" or "EUR". Defaults to the site's own currency.
- `destinations` (array, required): Destination codes from destinations_search ("FR", "EUR"). One code: the plans its page lists. Several: the plans that cover them all.
- `minDataGb` (number): Least data accepted, in GB. Unlimited plans always qualify.
- `minDays` (integer): Shortest validity accepted, in days.
- `unlimitedOnly` (boolean): Only plans with unlimited data.

### `devices_check` (~134 tokens)

Check eSIM compatibility

Check whether a phone or tablet supports eSIM against the compatible-device list simoptions.com publishes, by its model name ("iPhone 15 Pro", "Samsung Galaxy S24") or model code ("SM-S921B"). "yes" names the listed model. "unknown" means it is not on the list, which only holds compatible models: it is not a no, and the phone's settings tell whether it has an eSIM option.

Input parameters:

- `model` (string, required): The phone or tablet: its model name ("iPhone 15 Pro", "Samsung Galaxy S24") or model code ("SM-S921B").

## Diagnostics

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

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72

## Common questions

### What is the SimOptions MCP server?

SimOptions is an MCP server listed in the public MCP registry as com.simoptions/connector. Find and compare travel eSIM plans, check phone eSIM compatibility, and open each plan's page. This page covers its hosted endpoint (https://www.simoptions.com/api/connector/).

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

SimOptions scores 74 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 SimOptions MCP server expose?

SimOptions exposes 3 tools: destinations_search, plans_find, devices_check. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.

### Does the SimOptions MCP server require authentication?

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

### Is the SimOptions MCP server still maintained?

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

### What did VerifyMCP test on the SimOptions MCP server?

VerifyMCP ran 13 checks on SimOptions, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.simoptions.com/api/connector/
- Website: https://simoptions.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-simoptions-connector/api-connector-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-simoptions-connector/api-connector-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-simoptions-connector/api-connector-2.json
- HTML version of this page: https://verifymcp.io/servers/com-simoptions-connector/api-connector-2
