Roam2Go eSIM Catalog
REMOTE · ROAM2GO.COM · SCANNED OCT 1
Search travel eSIM data plans for 230+ destinations with live prices and purchase links.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1111 tokens (~370/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Roam2Go eSIM Catalog MCP server?
Roam2Go eSIM Catalog is a hosted endpoint at https://roam2go.com/wp-json/r2g-mcp/v1/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.
remote · roam2go.com
claude mcp add --transport http com-roam2go-esim-catalog 'https://roam2go.com/wp-json/r2g-mcp/v1/mcp'
{
"mcpServers": {
"com-roam2go-esim-catalog": {
"url": "https://roam2go.com/wp-json/r2g-mcp/v1/mcp"
}
}
} {
"servers": {
"com-roam2go-esim-catalog": {
"type": "http",
"url": "https://roam2go.com/wp-json/r2g-mcp/v1/mcp"
}
}
} [mcp_servers.com-roam2go-esim-catalog] url = "https://roam2go.com/wp-json/r2g-mcp/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-roam2go-esim-catalog": {
"type": "remote",
"url": "https://roam2go.com/wp-json/r2g-mcp/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-roam2go-esim-catalog --url 'https://roam2go.com/wp-json/r2g-mcp/v1/mcp' --transport streamable-http
mcp_servers:
com-roam2go-esim-catalog:
url: "https://roam2go.com/wp-json/r2g-mcp/v1/mcp" {
"McpServers": {
"com-roam2go-esim-catalog": {
"Transport": "http",
"Url": "https://roam2go.com/wp-json/r2g-mcp/v1/mcp"
}
}
} assistant mcp add com-roam2go-esim-catalog -t streamable-http -u 'https://roam2go.com/wp-json/r2g-mcp/v1/mcp'
{
"mcpServers": {
"com-roam2go-esim-catalog": {
"type": "http",
"url": "https://roam2go.com/wp-json/r2g-mcp/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_plan” rewrote its description, which is the text the model reads security
- Tool “search_plans” rewrote its description, which is the text the model reads security
- Schema quality: 309 → 370 ▼ functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_plans” rewrote its description, which is the text the model reads security
- 23 Sept 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_plans” rewrote its description, which is the text the model reads security
- Schema quality: 165 → 306 ▼ functional
- Schema quality: excellent → good functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Oct 2026 · Probed https://roam2go.com/wp-json/r2g-mcp/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.roam2go.com | CN=YR1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | RSA 2048 | SHA256-RSA | 6966b31d0bcb92c58876b50112339d992a3 |
| SANs: *.roam2go.com, roam2go.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of roam2go.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roam2go.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' https:; script-src-attr 'none'; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https: blob:; font-src 'self' data: https:; connect-src 'self' https: wss:; frame-src 'self' https:; media-src 'self' https:; object-src 'none'; base-uri 'self'; form-action 'self' https:; frame-ancestors 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self "https://js.stripe.com" "https://pay.google.com" "https://www.paypal.com"), publickey-credentials-get=(self "https://js.stripe.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roam2go.com/wp-json/r2g-mcp/v1/mcp | Verified | 200 | |
| http (plaintext) | http://roam2go.com/wp-json/r2g-mcp/v1/mcp | HTTPS enforced | 301 | https://roam2go.com/wp-json/r2g-mcp/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_plan Get eSIM plan ~76
Get one plan by its id (e.g. "R2G-7224"), including the purchase link, also in 7 languages ("product_urls" and "checkout_urls": ca, es, en, fr, it, de, pt; give the one in the language of the user).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_destinations List destinations ~24
List all destinations (country name + code + cheapest plan price in EUR).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_plans Search eSIM plans ~506
Search travel eSIM data plans by destination name. Returns plans with price (EUR, VAT included), data amount, validity days, activation policy and a direct purchase link. Matching is on the destination's own name in any major language, so a country name returns that country's local plans. Regional and global plans that cover that country are returned too, after the local ones, so asking for "France" also surfaces the Europe plan. You can still search a region by its own name, e.g. "Europe", "Asia", "Oceania", "North America", "Latin America", "Africa", "Caribbean Islands", "Middle East and North Africa", or "global" for worldwide plans. "matches" is the total number of plans found and "returned" is how many are in this response; raise "limit" (max 40) to see the rest. Unlimited plans carry a "fair_use" object with that plan's real figures: "gb_per_day" (GB per day at full speed; null when the plan declares no daily amount), "speed_after_mbps" (speed after that amount; when "gb_per_day" is null, the plan's top speed: say "up to" it; null if not stated), "never_cut" (true = the connection is never cut off) and "no_daily_quota" (true = no daily quota at all); "fair_use" is null when no figures are declared. Plans with calls carry a "voice" object: "minutes" and "international_calls" (false = calls within the destination country only, true = international calls with a US-based +1 number, null = not stated). Each plan also has "product_urls" and "checkout_urls": the same page and the same purchase link in Catalan (ca), Spanish (es), English (en), French (fr), Italian (it), German (de) and Portuguese (pt). Always give the user the link in the language they are writing in; use "en" for any other language.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Country name in any major language, e.g. "Japan", "Japon", "Japó" |
| limit | integer | – | Max results (default 12, max 40) |
| min_data_gb | number | – | Minimum data in GB (unlimited plans always match) |
| min_days | integer | – | Only plans valid at least this many days |
No output schema declared.
No examples provided.
What is the Roam2Go eSIM Catalog MCP server?
Roam2Go eSIM Catalog is an MCP server listed in the public MCP registry as com.roam2go/esim-catalog. Search travel eSIM data plans for 230+ destinations with live prices and purchase links. This page covers its hosted endpoint (https://roam2go.com/wp-json/r2g-mcp/v1/mcp).
Is the Roam2Go eSIM Catalog MCP server safe to use?
Roam2Go eSIM Catalog scores 82 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 Roam2Go eSIM Catalog MCP server expose?
Roam2Go eSIM Catalog exposes 3 tools: search_plans, get_plan, list_destinations. Their descriptions and schemas cost roughly 606 tokens of context every time the server is loaded.
Does the Roam2Go eSIM Catalog MCP server require authentication?
No. We connected to Roam2Go eSIM Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Roam2Go eSIM Catalog MCP server still maintained?
Roam2Go eSIM Catalog is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.