roam2go-catalog
Registry code: b410e76a9deeb51d
Search Roam2Go travel eSIM data plans (218 countries and territories, plus 17 regional and global plans) and get a direct purchase link. Prices include VAT. Always check each plan's "activation" field to tell the customer when validity starts: "first-usage" starts on first connection at the destination, "installation" starts when the eSIM is installed, and "unknown" means you should not state either — the purchase email always says which one applies. When showing how much data a plan includes, always use the "data_label" field verbatim (e.g. "500 MB", "5 GB", "unlimited"); never show the raw…
- endpoint
- https://roam2go.com/wp-json/r2g-mcp/v1/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is roam2go-catalog live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is roam2go-catalog free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does roam2go-catalog have?
- 3 tools: search_plans, get_plan, list_destinations.
- Is roam2go-catalog safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
- used for
- search travel esim plans by destination
- get an esim plan with purchase link
- list esim destinations
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_destinations reads open 16h ago
List all destinations (country name + code + cheapest plan price in EUR).
{ "type": "object", "properties": {} }arguments 4 linessearch_plans reads unknown 16h ago
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.
{ "type": "object", "required": [ "destination" ], "properties": { "limit": { "type": "integer", "description": "Max results (default 12, max 40)" }, "min_days": { "type": "integer", "description": "Only plans valid at least this many days" }, "destination": { "type": "string", "description": "Country name in any major language, e.g. \"Japan\", \"Japon\", \"Japó\"" }, "min_data_gb": { "type": "number", "description": "Minimum data in GB (unlimited plans always match)" } } }arguments 24 linesget_plan reads unknown 16h ago
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).
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" } } }arguments 11 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb410e76a9deeb51d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b410e76a9deeb51d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b410e76a9deeb51d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.