Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EMT Compute

REMOTE · EMTCOMPUTE.COM

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

Available components

56 Trust /100

Last scanned (5 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security51
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1344 tokens (~64/item across 21 items; 21 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1
    • 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 security
    • Schema quality: 1159 → 1344 ▼ functional
    • 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” functional
  • 4 Nov 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://emtcompute.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=emtcompute.com CN=WE1,O=Google Trust Services,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA256 dce89b4c8f69710e0e1ddb0f631829ab
SANs: emtcompute.com, staging.emtcompute.com, *.staging.emtcompute.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of emtcompute.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
emtcompute.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'self'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://emtcompute.com/mcp Verified 200
http (plaintext) http://emtcompute.com/mcp Inconclusive 405
MCP tools · 21 exposed · ~1,245 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
emt_attach_cluster_experiment ~149

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.

NameTypeReqDescription
clusterOrderstringyes–
configobject––
experiment–yes–
filesarray––
idempotency_keystringyes–
levelstring––
maxMinutesinteger––
namestringyes–
releaseClusterbooleanyes–
runsarrayyes–
seedinteger––
sshstring––

No output schema declared.

No examples provided.

emt_cancel_experiment ~55

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

NameTypeReqDescription
confirm_stopbooleanyes–
jobstringyes–

No output schema declared.

No examples provided.

emt_catalog ~56

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

NameTypeReqDescription
limitinteger––
modelstring––
offsetinteger––

No output schema declared.

No examples provided.

emt_cluster_quote ~41

Quote selected whole nodes on one fabric without renting.

NameTypeReqDescription
clusterstringyes–
hoursintegeryes–
nodesarrayyes–

No output schema declared.

No examples provided.

emt_clusters ~24

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emt_experiment_job ~43

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

NameTypeReqDescription
jobstringyes–

No output schema declared.

No examples provided.

emt_experiment_jobs ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emt_experiment_presets ~43

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

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

emt_experiment_quote ~105

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.

NameTypeReqDescription
countinteger––
environmentstring––
fp64boolean––
maxMinutesinteger––
minVraminteger––
modelstring––
nodestring––
nodesinteger––

No output schema declared.

No examples provided.

emt_monitor ~29

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

NameTypeReqDescription
orderstringyes–

No output schema declared.

No examples provided.

emt_orders ~20

Owned GPU orders and lifecycle states. Requires read scope.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emt_quote ~42

Create a fresh expiring GPU quote without renting or charging.

NameTypeReqDescription
countintegeryes–
hoursintegeryes–
nodestringyes–

No output schema declared.

No examples provided.

emt_rent ~117

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

NameTypeReqDescription
backupsboolean––
confirm_paid_rentalbooleanyes–
idempotency_keystringyes–
jupyterboolean––
namestringyes–
portsinteger––
quotestringyes–
sshstring––
templatestringyes–
volumestring––

No output schema declared.

No examples provided.

emt_rent_cluster ~85

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

NameTypeReqDescription
acknowledgeSlowNetworkboolean––
confirm_paid_rentalbooleanyes–
idempotency_keystringyes–
namestringyes–
quotestringyes–
sshstringyes–

No output schema declared.

No examples provided.

emt_start_experiment ~154

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.

NameTypeReqDescription
autoobject––
configobject––
confirm_paid_rentalbooleanyes–
experiment–yes–
filesarray––
idempotency_keystringyes–
levelstring––
namestringyes–
quotesarrayyes–
resumeobject––
runsarrayyes–
seedinteger––
sshstring––

No output schema declared.

No examples provided.

emt_templates ~17

Public GPU container templates for ordinary rentals.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emt_terminate ~55

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

NameTypeReqDescription
confirm_local_data_lossbooleanyes–
orderstringyes–

No output schema declared.

No examples provided.

emt_training_events ~90

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.

NameTypeReqDescription
afterinteger––
jobstringyes–
latestboolean––

No output schema declared.

No examples provided.

emt_training_job ~31

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

NameTypeReqDescription
jobstringyes–

No output schema declared.

No examples provided.

emt_training_jobs ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emt_training_recipe ~36

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

NameTypeReqDescription
jobstringyes–

No output schema declared.

No examples provided.

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.

remote · emtcompute.com

# add to Claude Code
claude mcp add --transport http com-emtcompute-emt-compute 'https://emtcompute.com/mcp'
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.