EMT Compute

com.emtcomputePublished by emtcompute.comOfficial publisherv1.2.0Updated Nov 6, 2026

GPU nodes and clusters, custom experiments, AI training and calculation reports for team workspaces.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureData & AnalyticsAI & ML

Overview

AI-generated overview

EMT Compute lets an assistant browse GPU offers, get quotes, rent paid GPU nodes or clusters, and inspect experiments and training jobs in an EMT workspace.

What you can do
  • Browse GPU offers, whole-node clusters, public templates and verified environments with CUDA versions and ports
  • Create expiring quotes for single GPUs, clusters and experiments, and list scientific experiment presets
  • Start paid rentals, cluster rentals and experiments, and attach work to an existing cluster
  • Inspect owned orders, experiment jobs, training jobs, recipes and training events with metrics
  • Read monitoring metrics and lifecycle state, cancel experiments and terminate rentals
When to use it
Useful when you want an assistant to compare GPU pricing, prepare and confirm a quote, then rent GPU capacity or launch a scientific or training workload in an EMT workspace, and later check job results and status.
Requirements
Remote endpoint at emtcompute.com over streamable HTTP. A bearer API key sent in the Authorization header, created in the intended EMT workspace with only the needed scopes. Rentals also need credit, accepted terms and spending authorization. Profile, terms and workspace management happen in the EMT console, not through MCP.
Before you install
Several tools spend real money: emt_rent, emt_rent_cluster and emt_start_experiment start paid rentals, and auto-continuation can rent extra segments up to a budget. Confirm costs with the user first, keep the launch payload and idempotency key, and never assume a rental stopped without checking release state. Terminating deletes local disks, and retained volumes and backups keep billing. Use a scoped key and a public SSH key only.

Installation

In SourceWeft

  1. Open EMT Compute in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.emtcompute%2Femt-compute/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "emt-compute": {
      "type": "http",
      "url": "https://emtcompute.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

22

emt_catalog

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

Parameterslimitmodeloffset

emt_clusters

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

Takes no parameters.

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.

Takes no parameters.

emt_environments

Verified environments (PyTorch, JAX, vLLM, TensorRT-LLM, ComfyUI, Unsloth) with their CUDA version and ports. Checked against the node before renting; they start an SSH server with the order's key.

Takes no parameters.

emt_experiment_presets

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

Parametersid

emt_orders

Owned GPU orders and lifecycle states. Requires read scope.

Takes no parameters.

emt_experiment_jobs

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

Takes no parameters.

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.

Parametersjobrequired

emt_training_jobs

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

Takes no parameters.

emt_training_job

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

Parametersjobrequired

emt_training_recipe

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

Parametersjobrequired

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 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.

Parametersjobrequiredafterlatest

emt_monitor

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

Parametersorderrequired

emt_quote

Create a fresh expiring GPU quote without renting or charging.

Parametersnoderequiredcountrequiredhoursrequired

emt_cluster_quote

Quote selected whole nodes on one fabric without renting.

Parametershoursrequirednodesrequiredclusterrequired

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.

Parametersfp64nodecountmodelnodesminVrammaxMinutesenvironment

emt_rent

Start a PAID GPU rental with exactly one of environment (verified, from emt_environments: preferred) or template. Requires explicit spending authorization, fresh quote, rent scope, credit and accepted terms. Store payload and key before requesting.

Parameterssshnamerequiredportsquoterequiredsetupvolumebackupsjupytertemplateenvironmentidempotency_keyrequiredconfirm_paid_rentalrequired

emt_rent_cluster

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

Parameterssshrequirednamerequiredquoterequiredidempotency_keyrequiredconfirm_paid_rentalrequiredacknowledgeSlowNetwork

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 solver. Auto-continuation may rent additional segments up to its budget. Review all costs before confirming.

Parameterssshautonamerequiredrunsrequiredseedfileslevelconfigquotesrequiredresumeexperimentrequiredidempotency_keyrequired+1 more

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

ParameterssshnamerequiredrunsrequiredseedfileslevelconfigexperimentrequiredmaxMinutesclusterOrderrequiredreleaseClusterrequiredidempotency_keyrequired

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.

Parametersjobrequiredconfirm_stoprequired

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.

Parametersorderrequiredconfirm_local_data_lossrequired

Version history

4
  1. v1.2.0LatestNov 6, 2026
  2. v1.1.1Nov 5, 2026
  3. v1.1.0Nov 5, 2026
  4. v1.0.0Nov 4, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.