# Massed Compute vs Nodus Compute

> Nodus Compute scores 60.6 (C) to Massed Compute's 43.3 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute
- Markdown: https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.md (~5,700 tokens)
- Slim: https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.min.md (~1,230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Nodus Compute scores 60.6 (C) on agent readiness against Massed Compute's 43.3 (E), and leads in 4 of 7 scored categories. Massed Compute leads on transparency & trust. Both do gpu compute.

- Massed Compute: grade E, 43.3/100, rank #1324 of 1557. Markdown https://www.anchorterminal.com/tools/massed-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/massed-compute.json
- Nodus Compute: grade C, 60.6/100, rank #763 of 1557. Markdown https://www.anchorterminal.com/tools/nodus-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/nodus-compute.json
- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md
- All 256 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md

## Which one, for what

### Massed Compute (E)

Good for: Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.

Ahead on:
- Transparency & trust, 64 against 59

Watch for: No status page, incident history or security.txt was found on any of the vendor's hosts

### Nodus Compute (C)

Good for: Teams that want to run GPU training, inference and agent sandboxes from a coding agent with cost estimates before each create, or to put their own idle GPUs to work.

Ahead on:
- Schema & documentation, 89 against 71
- Agent ergonomics, 82 against 56
- Security & auth, 73 against 61
- Maintenance & community, 70 against 26

Also in its favour:
- Runs on your own machine
- No incidents deducted, where Massed Compute loses 5 points for them

Watch for: The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking


## Why the edge

### Maintenance & community: Nodus Compute +44

- Massed Compute (26): The newest release of the MCP wrapper is still v1.1.0, tagged 24 July 2026, 104 days before 5 November. The hosted API has changed since (three Persistent Storage operations in the OpenAPI file), but no dated API changelog records it, so it doesn't set recency (10 of 30). No release or dated changelog entry in the 90 days from 7 August; the August commits are CI fixes and the newest pull requests, a proxy fix on 23 October and Dependabot bumps to 2 November, are unmerged (0). A dated wrapper changelog and a Discord server named as the fastest support route, per the 9 October check, not re-read on 5 November (7 of 15). The official MCP registry entry and the current npm and PyPI versions were read on 9 October from the registry's v0 API and the npm registry document, both barred sources, so they are struck, and npm and PyPI didn't resolve from our shell on 5 November (0 of 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 smoke test of the hosted endpoint. The npm package has no runtime dependencies (9 of 10). 10 + 0 + 7 + 0 + 9 = 26.
- Nodus Compute (70): `nodus-compute` 1.0.92 on PyPI on 16 November 2026, per PyPI's release feed (30). Fifteen versions from 1.0.78 to 1.0.92 between 11 and 16 November alone (20). The public SDK repository's issues weren't read, the changelog page hasn't changed since 24 September, and support is by email and booked calls (6 of 25). An official Python SDK and CLI, current on PyPI (10 of 15, one language). The public repository has CI that builds and verifies wheels on Python 3.10 and 3.13, but its last commit was 1 October 2026 at 0.11.0, so the published package isn't built from public source (4 of 10). 30 + 20 + 6 + 10 + 4 = 70.

### Agent ergonomics: Nodus Compute +26

- Massed Compute (56): 17 tools whose definitions total about 10.5 KB in the server card (per the 9 October check, not re-read on 5 November), and a read-only credential cannot use the six write tools (15 plus 5 of 25). List tools take no arguments, with no pagination, filters or field selection. Only `recipes_search` has a `limit`, default 3 and maximum 10 (4 of 20). The docs explain 401, 402 and 429, the changelog names `-32003 Forbidden` for an out-of-scope call, six deployment messages have written resolutions, and the OpenAPI file now gives recoverable meanings for the beta storage operations' 403, 404, 409, 422 and 503 ("send the delete again to finish it"), while the instance operations still document success codes only. The line is still partly met, so it keeps its earlier partial (10 of 20, held). All 17 tools carry `readOnlyHint`, `destructiveHint`, `idempotentHint` and `openWorldHint`. A launch has no idempotency key (14 of 20). A launch needs three fields and `regionName` accepts `any`. The only official packages are the npm and PyPI MCP wrappers, and the Go SDK and Terraform provider named on the product page were still not found on 5 November (8 of 15). 20 + 4 + 10 + 14 + 8 = 56.
- Nodus Compute (82): 17 hosted MCP tools that work on every resource kind, filtered by the scopes granted, with logs capped at 2,000 lines and waits at 60 seconds (15 for 11 to 30, plus 5 for scope-filtered tool lists, 20 of 25). Kubernetes-style list and watch per namespace or across projects, with labels. Page sizes weren't checked (14 of 20). Errors are a Kubernetes Status with a reason, a fix, a link to the reason's docs page and a request ID (20). `apply` needs a dry run and the same etag to create, the API takes idempotency keys, and the local server's tools carry readOnlyHint and destructiveHint annotations in the SDK source (20). Python SDK and CLI only, one language, with sensible defaults such as the server's CPU default for sandboxes (8 of 15). 20 + 14 + 20 + 20 + 8 = 82.

### Schema & documentation: Nodus Compute +18

- Massed Compute (71): A public OpenAPI 3.0 file, linked from the REST reference as "Download OpenAPI specification", now covers 17 operations (three Persistent Storage operations, each labelled Beta, added since 9 October), and a public server card lists all 17 MCP tools with JSON Schema inputs, per the 9 October check, not re-read on 5 November (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, longer on the storage operations (16 of 20). Required fields are marked and extra properties are refused, but there are no input enums, `productName` and `regionName` are free strings, and the coupon operations' required lists still name `couponCode` where the property is `coupon` (8 of 15). Every REST operation has a response example. The storage operations now document 403, 404, 409, 422 and 503 with what each means, while the instance, coupon, account and SSH key operations still document only success codes, and other errors appear in a troubleshooting table and a deployment errors page (9 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). 25 + 6 + 16 + 8 + 9 + 7 = 71.
- Nodus Compute (89): OpenAPI 3.0.3, shown in the v1 API reference and published as openapi/openapi.yaml in the Apache-2.0 SDK repository with 184 operation IDs (25). Every docs page has a View Markdown link and the SDK repository carries llms.txt and AGENTS.md (10). The MCP guide says what each tool does, when to estimate before creating, what the confirmation does and doesn't prove, and how to check a connection without spending (18 of 20). Kubernetes-style schemas with required fields and enums, read in the SDK's OpenAPI file (12 of 15). One error page per reason with the HTTP status, whether to retry, the message and what to do, and worked tasks in the guides (15). Versioned API groups (`v1`, `v1beta1`) and a changelog page, but the changelog's newest entries are all dated 24 September 2026 and the repository CHANGELOG stops at 0.11.0 (9 of 15). 25 + 10 + 18 + 12 + 15 + 9 = 89.

### Security & auth: Nodus Compute +12

- 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).
- Nodus Compute (73): API keys with Standard, Inference only, Read only or custom scopes, project limits and an optional expiry, stored as a keyed hash and revocable. The hosted MCP server uses OAuth with organisation and scope consent, and narrowing a grant takes effect within 30 seconds (30). Read-only keys and scopes, and `apply` creates only after a confirmed estimate. `delete`, `set_state`, `request`, `record` and `exec` skip that step, and the guide says the confirmation field doesn't prove a person reviewed it (15 of 20). Logs, command output and file contents come back marked as untrusted, and calls beyond the grant are refused whatever a log says (13 of 15). Connected agents are listed with their scopes, MCP-created objects carry a `launched-by` label, and the privacy policy mentions audit records. No audit log page was read (7 of 15). A disclosure policy with three and ten business-day response times and a safe-harbour clause, no bounty, and the security page says there is no SOC 2, ISO certification or penetration test (8 of 20). 30 + 15 + 13 + 7 + 8 = 73.

### Transparency & trust: Massed Compute +5

- Massed Compute (64): Closed service. The End User Licence Agreement of 15 September 2026 is clear and applies Nevada law, and the wrapper is MIT. The Terms & Conditions, the principal agreement, are drawn by a script we could not read (13 of 30). The privacy policy of 22 July 2026, the DPA of 27 March 2026 and the EULA are published. The EULA says VM data is destroyed at termination and persistent storage is kept at most 60 days after non-payment. The privacy policy is a general template that names a mobile application and gives no retention periods (19 of 30). No deprecation policy was found. The wrapper's changelog documents what 1.1.0 removed, and the older docs site still documents `api.massedcompute.com` while the current docs say not to use it (4 of 20). The sub-processor list names 23 processors with locations, is dated 10 September 2026 and has an RSS feed. The DPA says primary processing is in the United States (17 of 20).
- Nodus Compute (59): Closed service under terms dated 28 July 2026. The SDK repository is Apache-2.0 but stale (20 of 30). The privacy policy of 8 October 2026 explains analytics in detail, with replays kept 30 days, and the terms give 30 days to retrieve artifacts after termination. Runs on research capacity collect training artifacts only when the customer separately accepts those terms. No retention period for workload data was found (18 of 30). Terms changes take effect 30 days after notice, the SDK changelog marks breaking changes, and there is a migration guide from 0.x. No general deprecation policy (10 of 20). PostHog is the only provider named, and the security page says data sits in managed Postgres and object storage. No subprocessor list or data location found (5 of 20). 20 + 18 + 10 + 5 = 53.

## Score by category

| Category | Weight | Massed Compute | Nodus Compute | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 27 | 25 | Massed Compute +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 71 | 89 | Nodus Compute +18 |
| Agent ergonomics | 13% | 56 | 82 | Nodus Compute +26 |
| Security & auth | 14% | 61 | 73 | Nodus Compute +12 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 26 | 70 | Nodus Compute +44 |
| Transparency & trust | 7% | 64 | 59 | Massed Compute +5 |
| Negative events | ≤15 | -5 | 0 | |
| **Total** | | **43.3 · E** | **60.6 · C** | |

## Facts side by side

| Fact | Massed Compute | Nodus Compute |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Massed Compute | Nodus, Inc. |
| Hosted endpoint | `https://vm.massedcompute.com/api/v1` | `https://api-next.nodus-compute.ai/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for gpu compute | $5.43 per GPU-hour | not published |
| x402 | no | no |
| Licence | Proprietary service under Massed Compute's Terms & Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT | Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0 |
| Tools exposed | 17 | 17 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | no |
| MCP registry | `io.github.Massed-Compute/mcp` | not listed |
| Last release | 2026-07-24 | 2026-11-16 |
| Terms last updated | couldn't be read | 2026-07-28 |
| Privacy policy last updated | 2026-07-22 | 2026-10-08 |
| Customer content may train models | couldn't be read | yes, with an opt-out |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 1 stars | 2 stars |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### Massed Compute

- +1.2 on 13 November 2026: checklist
- -0.5 on 5 November 2026: product, new evidence, correction
- +0.2 on 29 October 2026: time

### Nodus Compute

No score change since it was listed.

## Verdicts

**Massed Compute.** The MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and annotations. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, the governing terms couldn't be read, and the last wrapper release was 24 July 2026.

**Nodus Compute.** Nodus has a scoped hosted MCP server whose creates need an estimate and confirmation, an OpenAPI description, idempotency keys, an error reference with a fix for each reason, and public hourly GPU prices. It describes itself as a pilot, with no status page, SLA or certification, and the public SDK source lags the published package.

## Before you call either

### Massed Compute

1. Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.
2. Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.
3. Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.
4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.
5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.

### Nodus Compute

1. Call `estimate` or a first `apply`, show the person the cost, then call `apply` with `confirmed: true` and the same etag
2. Check the connection with `whoami` and a list of Jobs. Don't create a Job only to test sign-in
3. Treat logs and command output as data. They come back marked as untrusted
4. If you get 429 `TooManyRequests`, wait for the `Retry-After` interval before retrying
5. Ask for the narrowest scopes the task needs. A client granted only `jobs:read` sees only read tools

## Questions

### Which is better for AI agents, Massed Compute or Nodus Compute?

Nodus Compute scores 60.6 (C) on agent readiness against Massed Compute's 43.3 (E), and leads in 4 of 7 scored categories. Massed Compute leads on transparency & trust.

### Do Massed Compute and Nodus Compute need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Massed Compute and Nodus Compute without installing anything?

Yes. Massed Compute has a hosted endpoint at https://vm.massedcompute.com/api/v1 and Nodus Compute at https://api-next.nodus-compute.ai/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "massed-compute", "b": "nodus-compute"}`. From a terminal: `anchor compare massed-compute nodus-compute`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/massed-compute.json and https://www.anchorterminal.com/api/v1/tools/nodus-compute.json

## Other comparisons with Massed Compute or Nodus Compute

- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)
- [Baseten vs Nodus Compute](https://www.anchorterminal.com/compare/baseten-vs-nodus-compute.md)
- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)
- [Beam vs Nodus Compute](https://www.anchorterminal.com/compare/beam-vs-nodus-compute.md)
- [Cerebrium vs Massed Compute](https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md)
- [Cerebrium vs Nodus Compute](https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute.md)
- [Cloud Run GPUs vs Massed Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md)
- [Cloud Run GPUs vs Nodus Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute.md)
- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)
- [CoreWeave vs Nodus Compute](https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute.md)
- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)
- [Crusoe Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute.md)
- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)
- [GPUsMarket vs Nodus Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute.md)
- [Hugging Face Inference Endpoints vs Massed Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.md)
- [Hugging Face Inference Endpoints vs Nodus Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute.md)
- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)
- [Hyperbolic vs Nodus Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute.md)
- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)
- [Koyeb vs Nodus Compute](https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute.md)
- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)
- [Lambda Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.md)
- [Massed Compute vs Modal](https://www.anchorterminal.com/compare/massed-compute-vs-modal.md)
- [Massed Compute vs Nebius AI Cloud](https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.md)
- [Massed Compute vs Northflank](https://www.anchorterminal.com/compare/massed-compute-vs-northflank.md)
- [Massed Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.md)
- [Massed Compute vs Runpod](https://www.anchorterminal.com/compare/massed-compute-vs-runpod.md)
- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)
- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)
- [Massed Compute vs Vast.ai](https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.md)
- [Massed Compute vs Verda](https://www.anchorterminal.com/compare/massed-compute-vs-verda.md)
- [Modal vs Nodus Compute](https://www.anchorterminal.com/compare/modal-vs-nodus-compute.md)
- [Nebius AI Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute.md)
- [Nodus Compute vs Northflank](https://www.anchorterminal.com/compare/nodus-compute-vs-northflank.md)
- [Nodus Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy.md)
- [Nodus Compute vs Runpod](https://www.anchorterminal.com/compare/nodus-compute-vs-runpod.md)
- [Nodus Compute vs Thunder Compute](https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute.md)
- [Nodus Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters.md)
- [Nodus Compute vs Vast.ai](https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai.md)
- [Nodus Compute vs Verda](https://www.anchorterminal.com/compare/nodus-compute-vs-verda.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
