# EMT Compute (remote · emtcompute.com)

GPU nodes and clusters, custom scientific experiments, AI training metrics and calculation reports.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `emtcompute.com`: 56/100 (this document), [markdown](https://verifymcp.io/servers/com-emtcompute-emt-compute/emtcompute.md), [page](https://verifymcp.io/servers/com-emtcompute-emt-compute/emtcompute)

## Channel facts

- Endpoint: `https://emtcompute.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (emt_attach_cluster_experiment).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1344 tokens (~64/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the EMT Compute MCP server?

EMT Compute is a hosted endpoint at https://emtcompute.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-emtcompute-emt-compute 'https://emtcompute.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-emtcompute-emt-compute]
url = "https://emtcompute.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-emtcompute-emt-compute": {
      "type": "remote",
      "url": "https://emtcompute.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-emtcompute-emt-compute --url 'https://emtcompute.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-emtcompute-emt-compute:
    url: "https://emtcompute.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-emtcompute-emt-compute": {
      "Transport": "http",
      "Url": "https://emtcompute.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-emtcompute-emt-compute -t streamable-http -u 'https://emtcompute.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 56, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “emt_catalog” rewrote its description, which is the text the model reads
- [security] Tool “emt_experiment_quote” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1159 → 1344
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “emt_training_events”
- [functional] New tool “emt_training_job”
- [functional] New tool “emt_training_jobs”
- [functional] New tool “emt_training_recipe”

### 2026-11-04 (score 55)

First indexed and scored.

## MCP tools (21)

### `emt_catalog` (~56 tokens)

Current GPU offers. Prices in EUR micro-units per GPU/hour; unknown metrics remain null. Paginated to keep responses small.

Input parameters:

- `limit` (integer)
- `model` (string)
- `offset` (integer)

### `emt_clusters` (~24 tokens)

Current whole-node cluster offers; fabric declarations do not establish independent EMT qualification.

### `emt_templates` (~17 tokens)

Public GPU container templates for ordinary rentals.

### `emt_experiment_presets` (~43 tokens)

List scientific presets or inspect one preset's parameters, equations, methods and custom-input schema. Does not run a calculation.

Input parameters:

- `id` (string)

### `emt_orders` (~20 tokens)

Owned GPU orders and lifecycle states. Requires read scope.

### `emt_experiment_jobs` (~25 tokens)

Owned experiment jobs, including reports and release state. Requires read scope.

### `emt_experiment_job` (~43 tokens)

Inspect an owned experiment and its authenticated result, output and calculation-report download links. Files are not sent into the model context.

Input parameters:

- `job` (string, required)

### `emt_training_jobs` (~28 tokens)

List owned AI training jobs. Requires read scope; does not start training or rent GPUs.

### `emt_training_job` (~31 tokens)

Inspect an owned training job, its settings, lifecycle and recorded outcome.

Input parameters:

- `job` (string, required)

### `emt_training_recipe` (~36 tokens)

Read the reproducible recipe for an owned training job, including model, dataset and training settings.

Input parameters:

- `job` (string, required)

### `emt_training_events` (~90 tokens)

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 with the greatest returned seq until an empty page. latest=true returns the most recent window only. Visible devices are not proof of GPU utilization.

Input parameters:

- `after` (integer)
- `job` (string, required)
- `latest` (boolean)

### `emt_monitor` (~29 tokens)

Metrics and lifecycle for an owned order. Missing telemetry is unknown.

Input parameters:

- `order` (string, required)

### `emt_quote` (~42 tokens)

Create a fresh expiring GPU quote without renting or charging.

Input parameters:

- `count` (integer, required)
- `hours` (integer, required)
- `node` (string, required)

### `emt_cluster_quote` (~41 tokens)

Quote selected whole nodes on one fabric without renting.

Input parameters:

- `cluster` (string, required)
- `hours` (integer, required)
- `nodes` (array, required)

### `emt_experiment_quote` (~105 tokens)

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.

Input parameters:

- `count` (integer)
- `environment` (string)
- `fp64` (boolean)
- `maxMinutes` (integer)
- `minVram` (integer)
- `model` (string)
- `node` (string)
- `nodes` (integer)

### `emt_rent` (~117 tokens)

Start a PAID GPU rental. Requires explicit spending authorization, fresh quote, rent scope, credit and accepted terms. Store payload and key before requesting.

Input parameters:

- `backups` (boolean)
- `confirm_paid_rental` (boolean, required)
- `idempotency_key` (string, required)
- `jupyter` (boolean)
- `name` (string, required)
- `ports` (integer)
- `quote` (string, required)
- `ssh` (string)
- `template` (string, required)
- `volume` (string)

### `emt_rent_cluster` (~85 tokens)

Start a PAID whole-node cluster rental. Public SSH key only. Confirm cost and fabric limits with the user first.

Input parameters:

- `acknowledgeSlowNetwork` (boolean)
- `confirm_paid_rental` (boolean, required)
- `idempotency_key` (string, required)
- `name` (string, required)
- `quote` (string, required)
- `ssh` (string, required)

### `emt_start_experiment` (~154 tokens)

Start a PAID scientific preset, customer script or command. Parameter sets distribute across quoted nodes; this does not automatically parallelize a single solver. Auto-continuation may rent additional segments up to its budget. Review all costs before confirming.

Input parameters:

- `auto` (object)
- `config` (object)
- `confirm_paid_rental` (boolean, required)
- `experiment` (required)
- `files` (array)
- `idempotency_key` (string, required)
- `level` (string)
- `name` (string, required)
- `quotes` (array, required)
- `resume` (object)
- `runs` (array, required)
- `seed` (integer)
- `ssh` (string)

### `emt_attach_cluster_experiment` (~149 tokens)

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 key. Whole cluster stops on completion/cancel; billing continues during preparation.

Input parameters:

- `clusterOrder` (string, required)
- `config` (object)
- `experiment` (required)
- `files` (array)
- `idempotency_key` (string, required)
- `level` (string)
- `maxMinutes` (integer)
- `name` (string, required)
- `releaseCluster` (boolean, required)
- `runs` (array, required)
- `seed` (integer)
- `ssh` (string)

### `emt_cancel_experiment` (~55 tokens)

Cancel an owned experiment and request release of all its GPU nodes or attached cluster. Unfinished work can be lost. Recheck releasing until false.

Input parameters:

- `confirm_stop` (boolean, required)
- `job` (string, required)

### `emt_terminate` (~55 tokens)

Terminate every node in an owned rental. Local disks are deleted; retained volumes and backups remain billed. Inspect status until release is confirmed.

Input parameters:

- `confirm_local_data_loss` (boolean, required)
- `order` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-emtcompute-emt-compute/emtcompute#diagnostics

## Score history

- 2026-11-05: 56
- 2026-11-04: 55

## Common questions

### What is the EMT Compute MCP server?

EMT Compute is an MCP server listed in the public MCP registry as com.emtcompute/emt-compute. GPU nodes and clusters, custom scientific experiments, AI training metrics and calculation reports. This page covers its hosted endpoint (https://emtcompute.com/mcp).

### Is the EMT Compute MCP server safe to use?

EMT Compute scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the EMT Compute MCP server expose?

EMT Compute exposes 21 tools: emt_catalog, emt_clusters, emt_templates, emt_experiment_presets, emt_orders, and 16 more. Their descriptions and schemas cost roughly 1,245 tokens of context every time the server is loaded.

### Does the EMT Compute MCP server require authentication?

No. We connected to EMT Compute without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EMT Compute MCP server still maintained?

EMT Compute is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://emtcompute.com/mcp
- Authorisation metadata: https://emtcompute.com/.well-known/oauth-protected-resource/mcp
- Website: https://emtcompute.com/integrations
- Changelog RSS feed: https://verifymcp.io/servers/com-emtcompute-emt-compute/emtcompute.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-emtcompute-emt-compute/emtcompute.json
- HTML version of this page: https://verifymcp.io/servers/com-emtcompute-emt-compute/emtcompute