Remote MCP · Endpoint
io.github.roamzy-io/mcp-server MCP server
No. io.github.roamzy-io/mcp-server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://roamzy.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.roamzy-io/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 146 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral.
- Repository
- https://github.com/roamzy-io/mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 146 ms |
| 10 hours ago | Handshake completed | 386 ms |
| 1 day ago | Handshake completed | 260 ms |
| 2 days ago | Handshake completed | 159 ms |
| 4 days ago | Handshake completed | 139 ms |
| 4 days ago | Handshake completed | 240 ms |
| 5 days ago | Handshake completed | 160 ms |
| 6 days ago | Handshake completed | 164 ms |
| 8 days ago | Handshake completed | 287 ms |
| 11 days ago | Handshake completed | 158 ms |
| 13 days ago | Handshake completed | 157 ms |
| 16 days ago | Handshake completed | 244 ms |
| 18 days ago | Handshake completed | 239 ms |
| 20 days ago | Handshake completed | 186 ms |
| 22 days ago | Handshake completed | 161 ms |
| 24 days ago | Handshake completed | 182 ms |
| 26 days ago | Handshake completed | 168 ms |
| 27 days ago | Handshake completed | 151 ms |
| 29 days ago | Handshake completed | 183 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 io.github.roamzy-io/mcp-server and makes no claim about it beyond what these checks measured.