# Emtcompute Emt Compute MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.emtcompute%2Femt-compute
Registry id: `mcp-registry/com.emtcompute/emt-compute`
Status: live (checked 2026-11-22T19:14:39.093Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 1034
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "emtcompute-emt-compute-mcp-server": {
      "type": "http",
      "url": "https://emtcompute.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http emtcompute-emt-compute-mcp-server https://emtcompute.com/mcp
```

## Tools (22)

- `emt_attach_cluster_experiment`: Attach work to an already rented dedicated 2–4-node cluster. Does NOT start SSH remotely: run emt_cluster.py locally with the returned job ID and your private k
- `emt_cancel_experiment`: Cancel an owned experiment and request release of all its GPU nodes or attached cluster. Unfinished work can be lost. Recheck releasing until false.
- `emt_catalog`: Current GPU offers. Prices in EUR micro-units per GPU/hour; unknown metrics remain null. Paginated to keep responses small.
- `emt_cluster_quote`: Quote selected whole nodes on one fabric without renting.
- `emt_clusters`: Current whole-node cluster offers; fabric declarations do not establish independent EMT qualification.
- `emt_environments`: Verified environments (PyTorch, JAX, vLLM, TensorRT-LLM, ComfyUI, Unsloth) with their CUDA version and ports. Checked against the node before renting; they star
- `emt_experiment_job`: Inspect an owned experiment and its authenticated result, output and calculation-report download links. Files are not sent into the model context.
- `emt_experiment_jobs`: Owned experiment jobs, including reports and release state. Requires read scope.
- `emt_experiment_presets`: List scientific presets or inspect one preset's parameters, equations, methods and custom-input schema. Does not run a calculation.
- `emt_experiment_quote`: Quote 1–4 nodes for an experiment; hours × hourly gives the GPU rental ceiling in micro-EUR. Reserve is only an initial hold, not total cost.
- `emt_monitor`: Metrics and lifecycle for an owned order. Missing telemetry is unknown.
- `emt_orders`: Owned GPU orders and lifecycle states. Requires read scope.
- `emt_quote`: Create a fresh expiring GPU quote without renting or charging.
- `emt_rent`: Start a PAID GPU rental with exactly one of environment (verified, from emt_environments: preferred) or template. Requires explicit spending authorization, fres
- `emt_rent_cluster`: Start a PAID whole-node cluster rental. Public SSH key only. Confirm cost and fabric limits with the user first.
- `emt_start_experiment`: Start a PAID scientific preset, customer script or command. Parameter sets distribute across quoted nodes; this does not automatically parallelize a single solv
- `emt_templates`: Public GPU container templates for ordinary rentals. Prefer emt_environments: public templates can be refused when their CUDA is newer than the node's driver.
- `emt_terminate`: Terminate every node in an owned rental. Local disks are deleted; retained volumes and backups remain billed. Inspect status until release is confirmed.
- `emt_training_events`: Read up to 100 training events with metrics, runtime and observed dataset hashes when recorded. For full history start after=0 and latest=false, then repeat wit
- `emt_training_job`: Inspect an owned training job, its settings, lifecycle and recorded outcome.
- `emt_training_jobs`: List owned AI training jobs. Requires read scope; does not start training or rent GPUs.
- `emt_training_recipe`: Read the reproducible recipe for an owned training job, including model, dataset and training settings.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
