io.xportl/xportl · v1.0.0 · communication
XportL is healthy: it completed an MCP handshake in 1467 ms and exposes 5 tools.
GPU fabric tools: NCCL benchmark analysis, degradation cost, cluster compatibility, XportL facts.
Endpoint: https://xportl.io/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 1467 ms |
| Last checked (UTC) | 2026-10-19T03:45:37.179Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-19T03:45:37.179Z | Healthy | 1467 |
get_xportl_overview | Returns cite-ready facts about XportL from xportl.io: what it does, the problem it solves, the eBPF → ClickHouse → GNN → Rust enforcement architecture, supported fabrics/GPUs/collectives/kernels, use cases, FAQ and company details (parent company, stage, NVIDIA Inception, contacts). |
analyze_nccl_benchmark | Analyzes nccl-tests / rccl-tests results (paste raw all_reduce_perf output, or give size/busbw points). Detects node and GPU counts from the output, compares large-message bus bandwidth with the fabric's NIC line rate (InfiniBand HDR/NDR/XDR, RoCE 100–800G), and flags data errors, degraded bandwidth |
calculate_fabric_degradation_cost | Estimates what silent fabric degradation (slow NCCL collectives, flapping links, congestion) costs a GPU cluster: throughput lost, GPU-hours and dollars per year, idle-GPU equivalent, cost per degraded hour, extra days on a training run, and the value of a recovery scenario (XportL publishes up to 4 |
check_cluster_compatibility | Checks a GPU cluster against XportL's published support matrix (Linux 5.8+ for eBPF, InfiniBand / RoCE v2 / NVLink, NVIDIA and AMD GPUs, NCCL / RCCL, on-prem / cloud / hybrid, host access for the eBPF agent). Returns a verdict (good fit / needs review / not ready), each check, and next steps. Anythi |
request_enterprise_demo | Sends the user's contact details and cluster summary to the XportL enterprise team to arrange a technical assessment or demo deployment. Before calling: collect name, work email, company and a summary (include benchmark, cost or compatibility results from this conversation), show the user exactly wh |