Skip to content
XportL logo

XportL MCP server

Which MCP servers are XportL's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to XportL

Whose server it is
  • Registry nameio.xportl/xportlverified in the MCP registry

The registry name sits under xportl.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools6
  • Server calls itselfxportl
  • Server version1.2.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 141 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-27
  • INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
  • Answered100% of days7 of 7 daily checks
  • Median first answer346 ms
  • Space in an agent's context≈ 2,880 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · find which GPU or link is slowing a collective
  • not sure · catch a stuck collective before the watchdog fires
  • cannot · retire repeat-failure nodes using a per-part failure ledger

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-27
  • get_xportl_overview

    Returns cite-ready facts about XportL from xportl.io: what it does, the problem it solves, the seven failure classes it detects, how it collects telemetry and acts, supported fabrics/GPUs/collectives/kernels, use cases, FAQ, company…

  • 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…

  • 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…

  • 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 /…

  • recommend_checkpoint_interval

    Recommends how often to checkpoint a training job using the Young and Daly formulas, from GPU count, blocking checkpoint write time, restart time and job MTTF (estimated from Meta's published 2024 reliability data when not given). Returns…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "xportl": {
      "type": "http",
      "url": "https://xportl.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http xportl https://xportl.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://xportl.io/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.