Remote MCP · Endpoint

XportL MCP server

No. XportL answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://xportl.io/mcp

The last check completed an MCP handshake.

Registry name
io.xportl/xportl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
GPU fabric tools: NCCL benchmark analysis, degradation cost, cluster compatibility, XportL facts.
Website
https://xportl.io/mcp-server/
Listing
From the official MCP registry (active).
Recent checks of XportL
CheckedResultHandshake
35 minutes agoHandshake completed199 ms
8 days agoHandshake completed207 ms
9 days agoHandshake completed158 ms
11 days agoHandshake completed166 ms
12 days agoHandshake completed179 ms
12 days agoHandshake completed190 ms
14 days agoHandshake completed168 ms
14 days agoHandshake completed166 ms
16 days agoHandshake completed191 ms
19 days agoHandshake completed159 ms
21 days agoHandshake completed97 ms
24 days agoHandshake completed171 ms
26 days agoHandshake completed164 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with XportL and makes no claim about it beyond what these checks measured.