Remote MCP · Endpoint

Xpress Flow Systems MCP server

No. Xpress Flow Systems answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://www.xpressflowsystems.com.ng/api/mcp

The last check completed an MCP handshake.

Registry name
ng.com.xpressflowsystems.www/esim-domains
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
No-sign-up eSIMs for 200+ countries, phone-number eSIMs, domains and proxies. You approve payment.
Listing
From the official MCP registry (active).
Recent checks of Xpress Flow Systems
CheckedResultHandshake
33 minutes agoHandshake completed94 ms
3 days agoHandshake completed83 ms
13 days agoHandshake completed807 ms
13 days agoHandshake completed157 ms
15 days agoHandshake completed785 ms
16 days agoHandshake completed823 ms
17 days agoHandshake completed167 ms
18 days agoHandshake completed127 ms
18 days agoHandshake completed63 ms
20 days agoHandshake completed961 ms
22 days agoHandshake completed221 ms
25 days agoHandshake completed880 ms
27 days agoHandshake completed862 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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 Xpress Flow Systems and makes no claim about it beyond what these checks measured.