mcp server
mcp
Massed Compute MCP — GPU inventory, VM lifecycle, billing, SSH keys, and setup recipes.
Description as published by the maintainer. Source
- version 1.1.0
- active
active — Registry entry last updated 2026-07-31.
What this server can do
The server requires authentication before it will list its tools (HTTP 401). We do not hold an account for it, so its functions are unknown to us. The functions below are the last successful declaration, not a fresh answer.
Endpoint status observed on . Source: https://vm.massedcompute.com/api/mcp.
17 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
account_billing- Retrieve billing settings for the account, including billing method and recharge configuration.
account_token_validation- Confirm that the Bearer token used to call this MCP server is a valid Massed Compute user API key.
coupon_accepted_products(coupon)- Look up which products a coupon code can be applied to, with current inventory availability. Required: coupon.
coupon_information(coupon)- Look up information about a coupon by code. Required: coupon.
gpu_inventory_list- Retrieve the comprehensive list of available GPU configurations, their specs, pricing, and current capacity per region.
images_list- Retrieve the catalog of preconfigured VM images available for deployment.
instances_get(uuid)- 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. Required: uuid.
instances_launch(coupon, command, imageId, sshKeys, regionName, productName, instanceName)- Deploy a new VM instance. Requires billing to be configured (recharge amount and threshold). This action incurs cost. Required: imageId, productName, regionName.
instances_list- 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.
instances_restart(instanceUuids)- Restart one or more VM instances by UUID, including instances that are stopped — this is also how a stopped instance is started again. Already-deleted instances are rejected. Required: instanceUuids.
instances_terminate(instanceUuids)- Terminate one or more VM instances by UUID, including instances that are still initializing or stopped. DESTRUCTIVE: this stops billing for the listed instances and permanently deletes their data; the action cannot be undone. Confirm with the user before invoking. Required: instanceUuids.
recipes_get(slug)- 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. Required: slug.
recipes_list- 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.
recipes_search(limit, query)- 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. Required: query.
ssh_keys_create(name, publicKey)- Add a new SSH public key to the authenticated account. Key names are restricted to letters, digits and spaces — a name like 'codex_ed25519' or 'my-laptop' is rejected. Required: name, publicKey.
ssh_keys_delete(id)- Remove an SSH key from the account. DESTRUCTIVE: any instances relying on this key may lose access. Confirm with the user before invoking. Required: id.
ssh_keys_list- List SSH keys associated with the authenticated account.
Last successful function declaration observed on . Source: https://vm.massedcompute.com/api/mcp. We list what the server declared; we do not call any of these functions.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 17 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | vm.massedcompute.com | |
| mcp endpoint status | auth_required | The server requires authentication before it will list its tools (HTTP 401). We do not hold an account for it, so its functions are unknown to us. | as of probe | vm.massedcompute.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json