Massed Compute vs Together GPU Clusters

Massed Compute 51

The newest release of the MCP wrapper is v1.1.0 of 24 July 2026, 77 days before the check. The hosted server has changed since, with fields in the server card that the July definitions lack, but no dated API changelog records it (20 of 30). One release and one dated changelog entry in the last 90 days (0). A dated wrapper changelog and a Discord server named as the fastest support route. No API changelog, and the repository shows six open issues or pull requests whose answers we did not read (7 of 15). Listed in the official MCP registry as io.github.Massed-Compute/mcp at 1.1.0, published 31 July 2026, with current npm and PyPI packages (15). CI tests Node 20 and 22 and Python 3.10 to 3.13 on three operating systems, with Dependabot, static analysis and a nightly check of the hosted endpoint. The npm package has no runtime dependencies (9 of 10).

Together GPU Clusters 75

Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75.

Massed Compute 69

A public OpenAPI 3.0 file covers the 14 REST operations, and a public server card lists all 17 MCP tools with JSON Schema inputs (25). massedcompute.com has an llms.txt that indexes marketing pages, and the vendor publishes an agent catalogue, the server card and four Markdown skills files. The docs sites have no llms.txt or Markdown copies (6 of 10). Tool descriptions state the purpose, the cost of a launch, when to search recipes first and when to confirm with the user. REST descriptions are one line each (16 of 20). Required fields are marked and extra properties are refused, but there are no enums, productName and regionName are free strings, and the OpenAPI file's required lists name image_id and couponCode where the properties are imageId and coupon (8 of 15). Every REST operation has a response example. Only 200 and 202 are documented, and errors appear only in a troubleshooting table and a deployment errors page (7 of 15). The path is versioned as /api/v1 and the MCP wrapper has a dated changelog. No API changelog was found (7 of 15).

Together GPU Clusters 92

Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92.

Massed Compute 20

Graded on the hosted lines for the MCP server and the REST API. No status page was found on the site, the docs, the pricing page or the repository (0). No incident history to read (5). The troubleshooting page documents a 429 for request limits with no figures (0). The same page says to wait a minute and retry, and every tool carries an idempotentHint, but instances_launch has no idempotency key (5 of 15). The on-demand page says 99.999 per cent uptime is guaranteed. No SLA document was found, the End User Licence Agreement promises support only under an order form or SLA, and the Terms & Conditions could not be read (0). The API is /api/v1, the server card is version 1.0.0 and nothing is labelled beta (10).

Together GPU Clusters 38

Read with the hosted lines. status.together.ai lists the website, the playground and serverless models with no component for GPU clusters, and a vendor page with no component for the product takes 15 in this run, as for Together's Code Sandbox and fine-tuning listings (15). No incident history for clusters can be read (5). No rate limits for the clusters API found (0). Together's docs give 429 and 503 backoff guidance for its APIs, per the inference listing's 1 November check, and the CLI has --non-interactive and --json for scripted retries, but creation has no idempotency key (8). No SLA for clusters found; the published 99% commitment covers provisioned inference throughput only (0). Generally available since 9 September 2025 and out of the CLI's beta paths since 22 October 2026, with preemptible nodes in preview (10). 15+5+0+8+0+10 = 38.

Massed Compute 61

OAuth with discovery from a 401 challenge, or named API tokens shown once and revoked one at a time. Both come in two tiers, read-only and full access, with no finer scopes. Secrets travel only in a header (26 of 30). The read-only tier blocks launch, restart, terminate and SSH key changes. Destructive tool descriptions ask the model to confirm with the user, and a published skill adds a disclosure step. No server-side confirmation was found (13 of 20). The MCP server redacts VM passwords from tool results. Recipes are vendor-written Markdown that tools tell the model to follow step by step, and the docs give no guidance on untrusted content (9 of 15). Connected Apps lists OAuth grants. No audit log or per-call history was found (3 of 15). The wrapper's SECURITY.md gives a disclosure address, a two-business-day acknowledgement and a 30-day fix target, and its CI runs static analysis and dependency audits. The site claims SOC 2 Type II and HIPAA with no report or trust page, and there is no security.txt or bug bounty (10 of 20).

Together GPU Clusters 68

Project-scoped API keys, revocable with optional expiry, read as Together's other listings read the same key model (30). Admin and editor roles with no read-only role. Only admins get the admin kubeconfig, which has cluster-admin rights, and OIDC lets editors use kubectl under RBAC. Deletes run without confirmation when --non-interactive is passed (8). The API returns cluster state, not third-party content (10). Invoices itemise reserved, on-demand and storage charges, and no audit log for cluster operations was found (5). security.txt with a HackerOne route, per the 1 November check of the inference listing (15). 30+8+10+5+15 = 68.