Remote MCP · Endpoint
roamflat Flat configurator MCP server
No. roamflat Flat configurator answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://roamflat.com/wp-json/roamflat/mcp
The last check completed an MCP handshake.
- Registry name
- com.roamflat/esim-catalog
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 394 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 66.7% from 18 checks
- Described by its publisher as
- Unlimited travel eSIMs at 5–50 Mbps: live quotes by country, speed and days, plus a buy link.
- Website
- https://roamflat.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 394 ms |
| 1 day ago | Handshake completed | 432 ms |
| 2 days ago | Handshake completed | 480 ms |
| 3 days ago | Handshake completed | 585 ms |
| 4 days ago | Handshake completed | 453 ms |
| 5 days ago | Handshake completed | 459 ms |
| 7 days ago | Handshake completed | 449 ms |
| 9 days ago | Handshake completed | 1.32 s |
| 12 days ago | Handshake completed | 603 ms |
| 14 days ago | Handshake completed | 819 ms |
| 16 days ago | Handshake completed | 408 ms |
| 18 days ago | Handshake completed | 462 ms |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with roamflat Flat configurator and makes no claim about it beyond what these checks measured.