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

io.github.Massed-Compute/mcp

REMOTE · VM.MASSEDCOMPUTE.COM · 3 COMPONENTS · SCANNED AUG 3

Massed Compute MCP — GPU inventory, VM lifecycle, billing, SSH keys, and setup recipes.

+2 this week 68 Trust /100
Trust breakdown (6 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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • 97% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4506 tokens (~83/item across 54 items; 17 tools + 37 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · vm.massedcompute.com

# add to Claude Code
claude mcp add --transport http massed-compute-mcp https://vm.massedcompute.com/api/mcp
# ~/.codex/config.toml
[mcp_servers.massed-compute-mcp]
url = "https://vm.massedcompute.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "massed-compute-mcp": {
      "type": "remote",
      "url": "https://vm.massedcompute.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add massed-compute-mcp --url https://vm.massedcompute.com/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  massed-compute-mcp:
    url: "https://vm.massedcompute.com/api/mcp"
// mcp.json
{
  "mcpServers": {
    "massed-compute-mcp": {
      "type": "http",
      "url": "https://vm.massedcompute.com/api/mcp"
    }
  }
}

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

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.

  • 3 Aug 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1420 → 4506 functional
    • The server now declares the “resources” capability functional
    • Schema quality: excellent → good functional
    • New resource “nginx-ssl” functional
    • New resource “collect-debug-bundle” functional
    • New resource “caddy-reverse-proxy-tls” functional
    • New resource “blackwell-musicgen” functional
    • New resource “vm-redis” functional
    • New resource “vm-postgresql” functional
    • New resource “vm-mysql” functional
    • New resource “ubuntu-network-debug” functional
    • New resource “server-preflight-check” functional
    • New resource “nvidia-smi-troubleshooting” functional
    • New resource “nginx-websocket-proxy” functional
    • New resource “nginx-static-server” functional
    • New resource “nginx-reverse-proxy” functional
    • New resource “nginx-load-balancer” functional
    • New resource “nginx-auth-gate” functional
    • New resource “multi-modality-ai-stack” functional
    • New resource “massed-compute-vm-setup-ssh” functional
    • New resource “massed-compute-vm-service-journal-audit-context” functional
    • New resource “massed-compute-vm-network-connectivity-context” functional
    • New resource “massed-compute-vm-lifecycle” functional
    • New resource “massed-compute-vm-health-inventory-context” functional
    • New resource “massed-compute-vm-hardening-protection” functional
    • New resource “massed-compute-vllm-openai-api” functional
    • New resource “massed-compute-systematic-debug” functional
    • New resource “massed-compute-new-project-onboarding” functional
    • New resource “massed-compute-local-datacenter-supabase” functional
    • New resource “massed-compute-llm-lora-training” functional
    • New resource “local-agi-hermes-llama-team” functional
    • New resource “l40-gpu-health-check” functional
    • New resource “jupyter-server” functional
    • New resource “install-lance-on-l40” functional
    • New resource “gpu-ollama-llm” functional
    • New resource “gpu-container-access-check” functional
    • New resource “firewall-ui-lab” functional
    • New resource “docker-installed” functional
    • New resource “cursor-skills-mcp-work-genre-packs” functional
    • New resource “cuda-version-check” functional
  • 2 Aug 26 +11
    • Schema quality: unverified → excellent functional
    • Schema quality: fail → pass functional
  • 1 Aug 26 −10
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: good → unverified functional
    • Schema quality: pass → fail functional
    • The server now declares the “resources” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 63

    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 3 Aug 2026 · Probed https://vm.massedcompute.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=massedcompute.com CN=WE1,O=Google Trust Services,C=US 12 Jun 2026 10 Sept 2026 ECDSA 256 ECDSA-SHA256 a6d14ec4d75508b21397767b2e89ce6a
SANs: massedcompute.com, *.massedcompute.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
DNSSEC insecure

Validation of vm.massedcompute.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
massedcompute.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=63072000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.wp.com https://s0.wp.com https://stats.wp.com https://*.zohopublic.com https://*.zohocdn.com https://*.termly.io https://*.google.com https://*.gstatic.com https://*.clarity.ms https://scripts.clarity.ms https://*.google-analytics.com https://*.googletagmanager.com https://*.cookieyes.com https://cdn-cookieyes.com https://*.wistia.com https://*.sentry-cdn.com https://*.helpscout.net https://*.crisp.chat https://*.logr-ingest.com https://*.logrocket.com https://*.metricool.com https://cdn.brevo.com https://cdn.by.wonderpush.com https://sibautomation.com https://*.sibautomation.com; connect-src 'self' https://api.stripe.com https://*.wp.com https://pixel.wp.com https://*.amplitude.com https://*.wistia.com https://*.sentry-cdn.com https://*.clarity.ms https://y.clarity.ms https://*.google.com https://*.google-analytics.com https://*.analytics.google.com https://*.g.doubleclick.net https://*.cookieyes.com https://l
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), autoplay=*, camera=(), display-capture=(self), encrypted-media=*, fullscreen=*, geolocation=(self), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(self), picture-in-picture=*, usb=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vm.massedcompute.com/api/mcp Verified 200
http (plaintext) http://vm.massedcompute.com/api/mcp HTTPS enforced 301 https://vm.massedcompute.com:443/api/mcp
MCP tools — 17 exposed · ~1,113 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.

Tool Tokens
account_billing ~23

Retrieve billing settings for the account, including billing method and recharge configuration.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

account_token_validation ~31

Confirm that the Bearer token used to call this MCP server is a valid Massed Compute user API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

coupon_accepted_products ~39

Look up which products a coupon code can be applied to, with current inventory availability.

NameTypeReqDescription
couponstringyesCoupon code to look up.

No output schema declared.

No examples provided.

coupon_information ~29

Look up information about a coupon by code.

NameTypeReqDescription
couponstringyesCoupon code to look up.

No output schema declared.

No examples provided.

gpu_inventory_list ~29

Retrieve the comprehensive list of available GPU configurations, their specs, pricing, and current capacity per region.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

images_list ~20

Retrieve the catalog of preconfigured VM images available for deployment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

instances_get ~54

Retrieve a single running VM instance by its UUID. Sensitive credentials (e.g. cleartext VM password) are redacted; fetch them through the REST API if needed.

NameTypeReqDescription
uuidstringyesUUID of the running instance.

No output schema declared.

No examples provided.

instances_launch ~155

Deploy a new VM instance. Requires billing to be configured (recharge amount and threshold). This action incurs cost.

NameTypeReqDescription
commandstringOptional startup command to run on boot.
couponstringOptional coupon code to apply at deploy time.
imageIdintegeryesID of the VM image to deploy.
instanceNamestringOptional human-readable name for the instance.
productNamestringyesProduct name of the GPU instance to deploy, e.g. 'gpu_1x_l40'.
regionNamestringyesRegion name. Use 'any' to let us choose.
sshKeysarrayOptional list of SSH key names to attach to the instance.

No output schema declared.

No examples provided.

instances_list ~42

Retrieve all running VM instances for the authenticated account. Sensitive credentials (e.g. cleartext VM password) are redacted; fetch them through the REST API if needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

instances_restart ~33

Restart one or more running VM instances by UUID.

NameTypeReqDescription
instanceUuidsarrayyesUUIDs of instances to restart.

No output schema declared.

No examples provided.

instances_terminate ~65

Terminate one or more running VM instances by UUID. DESTRUCTIVE: this stops billing for the listed instances and permanently deletes their data; the action cannot be undone. Confirm with the user before invoking.

NameTypeReqDescription
instanceUuidsarrayyesUUIDs of instances to terminate.

No output schema declared.

No examples provided.

recipes_get ~113

Fetch the full markdown body of a specific recipe by slug (typically a slug returned by recipes_search). The body contains Prerequisites, Provision, Configure, Verify, and Troubleshoot sections you should follow step-by-step, executing commands via SSH on the user's VM. Always read the full body before launching infrastructure — the recipe specifies the correct image, sku_class, and minimum specs that should drive your instances_launch call.

NameTypeReqDescription
slugstringyesThe kebab-case slug of the recipe (from recipes_list or recipes_search).

No output schema declared.

No examples provided.

recipes_list ~91

List every step-by-step setup recipe currently available for Massed Compute VMs. Prefer recipes_search when the user has a specific intent — call this only when the user asks open-ended questions like 'what can I set up on a VM?', 'what recipes do you have?', or wants to browse the catalogue. Returns metadata (slug, title, description, tags) only; call recipes_get for the full body.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recipes_search ~273

Find a step-by-step setup recipe matching a user's intent — installing, configuring, or deploying anything on a Linux VM (web servers, databases, container runtimes, dev environments, networking, security tooling, ML stacks — any software setup an LLM agent might be asked to perform). ALWAYS call this FIRST when a user asks to set up, install, deploy, run, host, or spin up any service or software on a Massed Compute VM, BEFORE calling instances_launch. The recipe returned will include the correct VM size, image, and step-by-step instructions the user expects you to follow. Examples that should trigger this tool: 'I want an nginx reverse proxy', 'spin up a jupyter notebook', 'set up HTTPS for my app', 'install docker', 'load balance traffic across backends', 'protect my dashboard with a login', 'host a postgres database', 'serve a static site', 'run an ollama server'. If no recipe matches, recipes_search returns no results — that's a useful negative signal that the requested setup may need ad-hoc instructions, not a reason to skip calling this tool.

NameTypeReqDescription
limitnumberMaximum number of matches to return (default 3, max 10).
querystringyesNatural-language description of what the user wants to set up.

No output schema declared.

No examples provided.

ssh_keys_create ~46

Add a new SSH public key to the authenticated account.

NameTypeReqDescription
namestringyesName for the SSH key.
publicKeystringyesOpenSSH-format public key contents.

No output schema declared.

No examples provided.

ssh_keys_delete ~52

Remove an SSH key from the account. DESTRUCTIVE: any instances relying on this key may lose access. Confirm with the user before invoking.

NameTypeReqDescription
idstringyesIdentifier of the SSH key to remove.

No output schema declared.

No examples provided.

ssh_keys_list ~18

List SSH keys associated with the authenticated account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.