{
  "data": {
    "a": {
      "slug": "massed-compute",
      "name": "Massed Compute",
      "vendor": "Massed Compute",
      "vendorUrl": "https://massedcompute.com",
      "company": "massedcompute.com",
      "kind": "http-api",
      "category": "gpu-compute",
      "summary": "Massed Compute is a US GPU cloud that rents NVIDIA GPU virtual machines by the hour from hardware it owns, with bare metal and clusters by quote. Agents use its REST API or a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/massed-compute",
      "markdownUrl": "https://www.anchorterminal.com/tools/massed-compute.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/massed-compute.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/massed-compute.json",
      "dns": "massed-compute.grade.anchorterminal.com",
      "repo": "https://github.com/Massed-Compute/massed-compute-mcp",
      "license": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://vm.massedcompute.com/api/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "massed-compute-mcp"
        },
        {
          "registry": "pypi",
          "name": "massed-compute-mcp"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve. The owner signs up in a browser, verifies an email address and creates a named API token at vm.massedcompute.com/settings/api, choosing Full access or Read only. The token is shown once, travels as a Bearer header and is revoked from the token table. The same token works for the REST API and the MCP server. MCP clients that send no token get a 401 with an OAuth challenge, and the owner signs in and approves full or read-only access. Grants are listed and revoked under Connected Apps. The older marketplace API on `api.massedcompute.com` issues keys only through support.",
      "pricing": "usage",
      "pricingNotes": "No free tier or trial credit was found. The owner adds a card or pays in crypto, makes a first deposit and sets an auto-recharge threshold of at least $5 before any launch. Running VMs are debited every minute at a published hourly rate. On 9 October 2026 a single A30 was $0.35 an hour, an RTX A6000 $0.57, an L40S $0.97, an A100 80 GB $1.35 and an H100 80 GB $2.73. No bandwidth charge per the pricing page. Bare metal, clusters and the marketplace API are by quote (https://vm.massedcompute.com/pricing).",
      "priceSummary": "Pay per use",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs, the two OpenAPI files, the MCP server card or the pricing page. The billing docs describe crypto top-ups made by the account owner, which is not a machine payment protocol (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": 17,
      "popularity": {
        "githubStars": 1,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://vm-docs.massedcompute.com",
      "llmsTxt": "https://massedcompute.com/llms.txt",
      "openapi": "https://vm-docs.massedcompute.com/redocusaurus/plugin-redoc-0.yaml",
      "registryName": "io.github.Massed-Compute/mcp",
      "capabilities": [
        "compute.gpu"
      ],
      "tags": [
        "hosted",
        "usage-priced",
        "openapi",
        "mcp",
        "oauth",
        "api-key",
        "read-only-keys",
        "node",
        "python",
        "card-required",
        "crypto-payments",
        "closed-source"
      ],
      "lastRelease": "2026-07-24",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 43.3,
        "grade": "E",
        "agentReady": false,
        "rank": 1324,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 21,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 56,
          "maintenance": 26,
          "payments": 30,
          "reliability": 27,
          "schema": 71,
          "security": 61,
          "transparency": 64
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-05"
        },
        "negative": -5,
        "negativeNotes": [
          "8 June 2026. The `instances_list` and `instances_get` MCP tools returned the cleartext VM password although their descriptions said it was redacted. Fixed in `massed-compute-mcp` 1.0.3 and later moved server-side, with rotation advice in the changelog. No GitHub advisory is published. Fixed and documented, so 3 points (https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md).",
          "9 October 2026. The product page lists SDKs for Go and a Terraform provider, webhooks and per-project quotas. None appears in the docs, the OpenAPI file or the vendor's public GitHub organisation. 2 points (https://massedcompute.com/products/inventory-api/)."
        ],
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "API tokens and OAuth grants come in read-only and full-access tiers, and tokens are revoked one at a time in the console",
          "A public server card lists all 17 MCP tools with JSON Schema inputs and `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations",
          "Hourly prices for 23 GPU configurations, from $0.35 for an A30 to $52.80 for eight B300s, are public without a login",
          "A public OpenAPI 3.0 file, linked as a download from the REST reference, covers 17 operations at `https://vm.massedcompute.com/api/v1`",
          "The sub-processor list names 23 processors with locations, was updated on 10 September 2026 and has an RSS feed for changes"
        ],
        "weaknesses": [
          "No status page, incident history or security.txt was found on any of the vendor's hosts",
          "A 429 answer exists but no rate limit figures are published, and only the storage operations document error responses in the OpenAPI file",
          "`POST /instance/launch` has no idempotency key, so a retried launch can start a second billed VM",
          "Until a fix dated 8 June 2026, `instances_list` and `instances_get` returned the cleartext VM password although their descriptions said it was redacted",
          "The product page lists Go and Terraform SDKs and webhooks that the docs, the OpenAPI file and the public GitHub organisation do not show",
          "A stopped instance is billed at the full hourly rate. Only termination ends billing, and it deletes the data"
        ],
        "agentNotes": [
          "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.",
          "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.",
          "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.",
          "Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.",
          "Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3.3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 43.3
          }
        ],
        "editorialScores": {
          "ergonomics": 56,
          "maintenance": 26,
          "payments": 30,
          "reliability": 27,
          "schema": 71,
          "security": 61,
          "transparency": 53
        },
        "provenanceScore": 74,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-05",
            "maintenance": "2026-11-05",
            "payments": "2026-11-05",
            "reliability": "2026-11-05",
            "schema": "2026-11-05",
            "security": "2026-11-05",
            "transparency": "2026-11-05"
          },
          "last": "2026-11-05",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-05",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install -g massed-compute-mcp",
        "claudeCode": "claude mcp add --transport http massed-compute https://vm.massedcompute.com/api/mcp --header \"Authorization: Bearer MC_TOKEN\"",
        "config": {
          "mcpServers": {
            "massed-compute": {
              "headers": {
                "Authorization": "Bearer MC_TOKEN"
              },
              "type": "http",
              "url": "https://vm.massedcompute.com/api/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/compute.gpu",
        "tool": "https://letme.dev/massed-compute"
      },
      "area": "models",
      "unitPrices": [
        {
          "item": "A30 24 GB VM",
          "unit": "gpu-hour",
          "usd": 0.35,
          "note": "Billed per minute"
        },
        {
          "item": "RTX A5000 24 GB VM",
          "unit": "gpu-hour",
          "usd": 0.44,
          "note": "Billed per minute"
        },
        {
          "item": "RTX A6000 48 GB VM",
          "unit": "gpu-hour",
          "usd": 0.57,
          "note": "Billed per minute. An alternative configuration is $0.55"
        },
        {
          "item": "RTX 6000 Ada 48 GB VM",
          "unit": "gpu-hour",
          "usd": 0.79,
          "note": "Billed per minute"
        },
        {
          "item": "L40 48 GB VM",
          "unit": "gpu-hour",
          "usd": 0.86,
          "note": "Billed per minute"
        },
        {
          "item": "RTX PRO 4500 Blackwell 32 GB VM",
          "unit": "gpu-hour",
          "usd": 0.92,
          "note": "Billed per minute"
        },
        {
          "item": "L40S 48 GB VM",
          "unit": "gpu-hour",
          "usd": 0.97,
          "note": "Billed per minute"
        },
        {
          "item": "A100 80 GB VM",
          "unit": "gpu-hour",
          "usd": 1.35,
          "note": "Billed per minute. SXM4 and DGX variants are $1.38"
        },
        {
          "item": "RTX PRO 6000 Blackwell 96 GB VM",
          "unit": "gpu-hour",
          "usd": 2.19,
          "note": "Billed per minute"
        },
        {
          "item": "H100 80 GB VM",
          "unit": "gpu-hour",
          "usd": 2.73,
          "note": "Billed per minute. H100 NVL is $3.11 and H100 SXM5 $3.14"
        },
        {
          "item": "H200 NVL 141 GB VM",
          "unit": "gpu-hour",
          "usd": 3.62,
          "note": "Billed per minute"
        },
        {
          "item": "B200 SXM6 VM, 8 GPUs",
          "unit": "gpu-hour",
          "usd": 5.43,
          "note": "Sold only as eight GPUs at $43.46 an hour. Our division, rounded"
        },
        {
          "item": "B300 SXM6 VM, 8 GPUs",
          "unit": "gpu-hour",
          "usd": 6.6,
          "note": "Sold only as eight GPUs at $52.80 an hour. Our division"
        }
      ],
      "provenance": {
        "legalEntity": "Massed Compute, Inc.",
        "domain": "massedcompute.com",
        "domainRegistered": "2021-10-28",
        "endpointOnVendorDomain": true,
        "terms": "https://massedcompute.com/legal/terms-conditions/",
        "privacy": "https://massedcompute.com/legal/privacy-policy/",
        "statusPage": "",
        "changelog": "https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The Terms \u0026 Conditions page is the document the DPA calls the Principal Agreement. Its body is an embedded Termly viewer drawn by script, and we could not read it.",
          "The End User Licence Agreement, last updated 15 September 2026, names Massed Compute, Inc. of Las Vegas, Nevada, and applies Nevada law. The older docs site's footer says Massed Compute LLC.",
          "The privacy policy, last updated 22 July 2026, covers the website, a mobile application and the Services in general.",
          "The REST API and the MCP server answer at vm.massedcompute.com, on the vendor domain.",
          "/.well-known/security.txt answers 404 on massedcompute.com and on vm.massedcompute.com.",
          "RDAP for massedcompute.com gives a registration date of 2021-10-28.",
          "No status page was found on the site, the docs or the pricing page.",
          "The changelog linked is the MCP wrapper's. No API changelog was found.",
          "A Data Processing Agreement, last modified 27 March 2026, and a sub-processor list, last updated 10 September 2026, are published."
        ],
        "score": 74
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/massed-compute.json",
      "live": {
        "slug": "massed-compute",
        "probe": {
          "target": "https://vm.massedcompute.com/api/v1",
          "method": "get",
          "lastAt": "2026-11-18T23:01:40.001263473Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 559,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 568,
          "p95ms24h": 761,
          "samples24h": 241,
          "samples30d": 7840,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 231,
              "ok": 231
            }
          ],
          "since": "2026-10-09T00:00:00Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "Massed-Compute/massed-compute-mcp",
            "version": "v1.1.0",
            "released": "2026-07-24",
            "seenAt": "2026-11-18T18:04:56.897544848Z"
          },
          {
            "registry": "mcp-registry",
            "name": "io.github.Massed-Compute/mcp",
            "version": "1.1.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          },
          {
            "registry": "npm",
            "name": "massed-compute-mcp",
            "version": "1.1.0",
            "seenAt": "2026-11-18T18:04:56.175932584Z"
          },
          {
            "registry": "pypi",
            "name": "massed-compute-mcp",
            "version": "1.1.0",
            "released": "2026-07-24",
            "seenAt": "2026-11-18T18:04:56.578591104Z"
          }
        ],
        "githubStars": 1,
        "npmWeekly": 84,
        "pypiWeekly": 28,
        "securityTxt": {
          "url": "https://massedcompute.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:29:53.619271121Z"
        },
        "llmsTxt": {
          "url": "https://massedcompute.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:00.65532128Z"
        },
        "domain": {
          "domain": "massedcompute.com",
          "registered": "2021-10-28",
          "source": "https://rdap.verisign.com/com/v1/domain/massedcompute.com",
          "checkedAt": "2026-11-15T15:27:06.001596211Z"
        },
        "pages": [
          {
            "url": "https://raw.githubusercontent.com/Massed-Compute/massed-compute-mcp/main/CHANGELOG.md",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-18T21:52:50.652650336Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "7fa22cb79429"
          },
          {
            "url": "https://vm.massedcompute.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:57:38.43968964Z",
            "changedAt": "2026-11-17T21:16:56.259897235Z",
            "fingerprint": "86a76d79f15a"
          },
          {
            "url": "https://massedcompute.com/legal/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:48:02.938854857Z",
            "changedAt": "2026-10-15T21:30:11.503135109Z",
            "fingerprint": "d9918bcc127e"
          },
          {
            "url": "https://massedcompute.com/legal/terms-conditions/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:48:05.046889205Z",
            "changedAt": "2026-11-17T21:07:16.002306596Z",
            "fingerprint": "4ef818a6c337"
          }
        ],
        "mcpTools": {
          "url": "https://vm.massedcompute.com/api/mcp",
          "checkedAt": "2026-11-18T04:25:54.147350275Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:46:11.470870377Z"
        },
        "github": {
          "repo": "massed-compute/massed-compute-mcp",
          "checkedAt": "2026-11-16T12:22:12.593451854Z",
          "stars": 1,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-11T22:14:18Z",
          "openIssues": 0,
          "openPRs": 7,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 4,
          "ci": {
            "branch": "main",
            "runs": 13,
            "success": 12,
            "failure": 1,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-11-11T22:13:29Z"
          }
        },
        "updatedAt": "2026-11-18T23:01:40.001263473Z"
      },
      "streak": {
        "days": 40,
        "from": "2026-10-09",
        "sinceWatching": true,
        "best": 40
      }
    },
    "answer": "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 \u0026 trust.",
    "b": {
      "slug": "nodus-compute",
      "name": "Nodus Compute",
      "vendor": "Nodus, Inc.",
      "vendorUrl": "https://www.nodus-compute.ai",
      "company": "nodus-compute.ai",
      "kind": "http-api",
      "category": "gpu-compute",
      "summary": "Nodus Compute runs training, fine-tuning, inference endpoints, agent sandboxes and batch jobs on rented GPUs or on the customer's own machines, through a Kubernetes-style HTTP API, a Python SDK and CLI, and a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/nodus-compute",
      "markdownUrl": "https://www.anchorterminal.com/tools/nodus-compute.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nodus-compute.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nodus-compute.json",
      "dns": "nodus-compute.grade.anchorterminal.com",
      "repo": "https://github.com/nodus-compute/Nodus-sdk-python",
      "license": "Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api-next.nodus-compute.ai/mcp",
      "packages": [
        {
          "registry": "pypi",
          "name": "nodus-compute"
        }
      ],
      "auth": "mixed",
      "authNotes": "API keys (`nodus_sk_live_`) sent as `Authorization: Bearer` or `NODUS_API_KEY`, created in the console or with `nodus create apikey`. Each key has Standard, Inference only, Read only or custom scopes, optional project limits and an optional expiry, and is stored as a keyed hash. The hosted MCP server uses OAuth, with a consent page that picks the organisation and scopes. Grants can be narrowed or deleted, taking effect within 30 seconds. A new organisation needs a verified email and card.",
      "pricing": "usage",
      "pricingNotes": "Hourly prices are published per GPU and CPU configuration, such as $2.600 for an H100 SXM, $1.090 for an A100 80 GB, $0.290 for an RTX 4090 and $0.0075 for 1 vCPU with 1 GiB. Usage draws on prepaid credits, with auto-recharge, budgets and spending caps. A new organisation needs a verified card, though verification buys no credits. Reserved GPUs and clusters are quoted on request.",
      "priceSummary": "$0.0075 / vCPU-hr",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the MCP guide, the pricing page or the error reference (checked 2026-11-18). Applying a TopUp through MCP returns a checkout link for the person to open.",
        "endpoints": []
      },
      "toolCount": 17,
      "popularity": {
        "githubStars": 2,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://www.nodus-compute.ai/docs/",
      "openapi": "https://github.com/nodus-compute/Nodus-sdk-python/blob/main/openapi/openapi.yaml",
      "capabilities": [
        "compute.gpu",
        "compute.batch",
        "compute.endpoints",
        "compute.containers",
        "sandbox.code"
      ],
      "tags": [
        "hosted",
        "usage",
        "gpu",
        "mcp",
        "remote-mcp",
        "oauth",
        "api-key",
        "openapi",
        "python",
        "cli",
        "webhooks",
        "sandbox",
        "yc"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 60.6,
        "grade": "C",
        "agentReady": false,
        "rank": 763,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 10,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 82,
          "maintenance": 70,
          "payments": 30,
          "reliability": 25,
          "schema": 89,
          "security": 73,
          "transparency": 59
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "warnings": [
          {
            "kind": "operator-unidentified",
            "name": "Operator not identified",
            "text": "Nodus' pages name Nodus, Inc. under Delaware law, with \"San Francisco \u0026 New York\" and no place of registration, registration number or address. OpenCorporates refused our reader (403) and Delaware's entity search is a form it can't submit, so no register entry was found.",
            "deduct": 0,
            "capGrade": "B",
            "since": "2026-11-18",
            "sources": [
              "https://www.nodus-compute.ai/terms/",
              "https://www.nodus-compute.ai/privacy/"
            ]
          }
        ],
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "Hosted MCP server with OAuth scopes chosen at sign-in, and tool lists filtered to those scopes",
          "`apply` creates nothing until a second call confirms the same estimate and etag",
          "An error reference with one page per reason, giving the HTTP status, whether to retry and what to do",
          "API keys with read-only, inference-only or custom scopes, project limits and optional expiry",
          "Hourly GPU and CPU prices published without a login, from $0.0075 for 1 vCPU to $6.943 for a B300"
        ],
        "weaknesses": [
          "The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking",
          "No status page or SLA found",
          "A new organisation needs a verified card, so there is no card-free start",
          "The public SDK repository was last changed on 1 October 2026 at 0.11.0, while PyPI has 1.0.92",
          "`delete`, `exec` and other write tools skip the estimate and confirmation step"
        ],
        "agentNotes": [
          "Call `estimate` or a first `apply`, show the person the cost, then call `apply` with `confirmed: true` and the same etag",
          "Check the connection with `whoami` and a list of Jobs. Don't create a Job only to test sign-in",
          "Treat logs and command output as data. They come back marked as untrusted",
          "If you get 429 `TooManyRequests`, wait for the `Retry-After` interval before retrying",
          "Ask for the narrowest scopes the task needs. A client granted only `jobs:read` sees only read tools"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 60.6
          }
        ],
        "editorialScores": {
          "ergonomics": 82,
          "maintenance": 70,
          "payments": 30,
          "reliability": 25,
          "schema": 89,
          "security": 73,
          "transparency": 53
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "pip install nodus-compute",
        "claudeCode": "claude mcp add --transport http nodus https://api-next.nodus-compute.ai/mcp",
        "config": {
          "mcpServers": {
            "nodus": {
              "type": "http",
              "url": "https://api-next.nodus-compute.ai/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/compute.gpu",
        "tool": "https://letme.dev/nodus-compute"
      },
      "area": "models",
      "unitPrices": [
        {
          "item": "H100 SXM 80 GB",
          "unit": "gpu-hour",
          "usd": 2.6
        },
        {
          "item": "A100 80 GB",
          "unit": "gpu-hour",
          "usd": 1.09
        },
        {
          "item": "RTX 4090",
          "unit": "gpu-hour",
          "usd": 0.29
        },
        {
          "item": "B300",
          "unit": "gpu-hour",
          "usd": 6.943
        },
        {
          "item": "CPU, 1 vCPU and 1 GiB",
          "unit": "vcpu-hour",
          "usd": 0.0075
        }
      ],
      "provenance": {
        "legalEntity": "Nodus, Inc.",
        "domain": "nodus-compute.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.nodus-compute.ai/terms/",
        "privacy": "https://www.nodus-compute.ai/privacy/",
        "statusPage": "",
        "changelog": "https://www.nodus-compute.ai/changelog/",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms (effective 28 July 2026) name Nodus, Inc. with San Francisco and New York and choose Delaware law. No place of incorporation, registration number or street address was found on any page read.",
          "The privacy policy is effective 8 October 2026.",
          "www.nodus-compute.ai robots.txt allowed every page read on 18 November 2026.",
          "No status page is linked from the site or the docs. The security page gives a disclosure policy with response times. /.well-known/security.txt returned 404.",
          "The domain's registration date wasn't looked up."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/nodus-compute.json",
      "live": {
        "slug": "nodus-compute",
        "probe": {
          "target": "https://api-next.nodus-compute.ai/mcp",
          "method": "get",
          "lastAt": "2026-11-18T23:01:43.19041236Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 314,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 362,
          "p95ms24h": 1308,
          "samples24h": 14,
          "samples30d": 14,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 14,
              "ok": 14
            }
          ],
          "since": "2026-11-18T21:38:16.078618535Z"
        },
        "updatedAt": "2026-11-18T23:01:43.19041236Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 44,
        "category": "maintenance",
        "leads": "nodus-compute",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "`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."
        },
        "scores": {
          "a": 26,
          "b": 70
        }
      },
      {
        "by": 26,
        "category": "ergonomics",
        "leads": "nodus-compute",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 56,
          "b": 82
        }
      },
      {
        "by": 18,
        "category": "schema",
        "leads": "nodus-compute",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 71,
          "b": 89
        }
      },
      {
        "by": 12,
        "category": "security",
        "leads": "nodus-compute",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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).",
          "b": "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."
        },
        "scores": {
          "a": 61,
          "b": 73
        }
      },
      {
        "by": 5,
        "category": "transparency",
        "leads": "massed-compute",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service. The End User Licence Agreement of 15 September 2026 is clear and applies Nevada law, and the wrapper is MIT. The Terms \u0026 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).",
          "b": "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."
        },
        "scores": {
          "a": 64,
          "b": 59
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Massed Compute",
        "b": "Nodus, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://vm.massedcompute.com/api/v1",
        "b": "https://api-next.nodus-compute.ai/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$5.43 per GPU-hour",
        "b": "not published",
        "name": "Price for gpu compute"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT",
        "b": "Proprietary hosted service under the Nodus Terms of Service. The Python SDK repository is Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "17",
        "b": "17",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "io.github.Massed-Compute/mcp",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-07-24",
        "b": "2026-11-16",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "2026-07-28",
        "name": "Terms last updated"
      },
      {
        "a": "2026-07-22",
        "b": "2026-10-08",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "yes, with an opt-out",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "1 stars",
        "b": "2 stars",
        "name": "Popularity"
      },
      {
        "a": "3.3/5 (4)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 trust.",
        "question": "Which is better for AI agents, Massed Compute or Nodus Compute?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Massed Compute and Nodus Compute need an API key?"
      },
      {
        "answer": "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.",
        "question": "Can an agent call Massed Compute and Nodus Compute without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Transparency \u0026 trust, 64 against 59"
        ],
        "also": null,
        "goodFor": "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.",
        "slug": "massed-compute",
        "watchFor": "No status page, incident history or security.txt was found on any of the vendor's hosts"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 89 against 71",
          "Agent ergonomics, 82 against 56",
          "Security \u0026 auth, 73 against 61",
          "Maintenance \u0026 community, 70 against 26"
        ],
        "also": [
          "Runs on your own machine",
          "No incidents deducted, where Massed Compute loses 5 points for them"
        ],
        "goodFor": "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.",
        "slug": "nodus-compute",
        "watchFor": "The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking"
      }
    ],
    "history": {
      "massed-compute": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.2,
          "from": 42.1,
          "fromGrade": "E",
          "to": 43.3,
          "toGrade": "E"
        },
        {
          "causes": [
            "product",
            "evidence",
            "correction"
          ],
          "date": "2026-11-05",
          "delta": -0.5,
          "from": 42.6,
          "fromGrade": "E",
          "to": 42.1,
          "toGrade": "E"
        },
        {
          "causes": [
            "time"
          ],
          "date": "2026-10-29",
          "delta": 0.2,
          "from": 42.4,
          "fromGrade": "E",
          "to": 42.6,
          "toGrade": "E"
        }
      ],
      "nodus-compute": null
    },
    "job": {
      "capability": "compute.gpu",
      "name": "GPU compute"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute.json",
        "title": "Baseten vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/baseten-vs-nodus-compute.json",
        "title": "Baseten vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/baseten-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-massed-compute.json",
        "title": "Beam vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/beam-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute.json",
        "title": "Beam vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/beam-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.json",
        "title": "Cerebrium vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute.json",
        "title": "Cerebrium vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.json",
        "title": "Cloud Run GPUs vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute.json",
        "title": "Cloud Run GPUs vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.json",
        "title": "CoreWeave vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/coreweave-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute.json",
        "title": "CoreWeave vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.json",
        "title": "Crusoe Cloud vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute.json",
        "title": "Crusoe Cloud vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.json",
        "title": "GPUsMarket vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute.json",
        "title": "GPUsMarket vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.json",
        "title": "Hugging Face Inference Endpoints vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute.json",
        "title": "Hugging Face Inference Endpoints vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.json",
        "title": "Hyperbolic vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute.json",
        "title": "Hyperbolic vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.json",
        "title": "Koyeb vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/koyeb-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute.json",
        "title": "Koyeb vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute.json",
        "title": "Lambda Cloud vs Massed Compute",
        "url": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.json",
        "title": "Lambda Cloud vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/lambda-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-modal.json",
        "title": "Massed Compute vs Modal",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-modal"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.json",
        "title": "Massed Compute vs Nebius AI Cloud",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank.json",
        "title": "Massed Compute vs Northflank",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.json",
        "title": "Massed Compute vs Replicate Deployments",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod.json",
        "title": "Massed Compute vs Runpod",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.json",
        "title": "Massed Compute vs Thunder Compute",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.json",
        "title": "Massed Compute vs Together GPU Clusters",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.json",
        "title": "Massed Compute vs Vast.ai",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.json",
        "title": "Massed Compute vs Verda",
        "url": "https://www.anchorterminal.com/compare/massed-compute-vs-verda"
      },
      {
        "json": "https://www.anchorterminal.com/compare/modal-vs-nodus-compute.json",
        "title": "Modal vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/modal-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute.json",
        "title": "Nebius AI Cloud vs Nodus Compute",
        "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-northflank.json",
        "title": "Nodus Compute vs Northflank",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-northflank"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy.json",
        "title": "Nodus Compute vs Replicate Deployments",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-runpod.json",
        "title": "Nodus Compute vs Runpod",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-runpod"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute.json",
        "title": "Nodus Compute vs Thunder Compute",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters.json",
        "title": "Nodus Compute vs Together GPU Clusters",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai.json",
        "title": "Nodus Compute vs Vast.ai",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nodus-compute-vs-verda.json",
        "title": "Nodus Compute vs Verda",
        "url": "https://www.anchorterminal.com/compare/nodus-compute-vs-verda"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 2,
        "edge": "massed-compute",
        "key": "reliability",
        "massed-compute": 27,
        "name": "Reliability",
        "nodus-compute": 25,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 18,
        "edge": "nodus-compute",
        "key": "schema",
        "massed-compute": 71,
        "name": "Schema \u0026 documentation",
        "nodus-compute": 89,
        "weight": 13
      },
      {
        "by": 26,
        "edge": "nodus-compute",
        "key": "ergonomics",
        "massed-compute": 56,
        "name": "Agent ergonomics",
        "nodus-compute": 82,
        "weight": 13
      },
      {
        "by": 12,
        "edge": "nodus-compute",
        "key": "security",
        "massed-compute": 61,
        "name": "Security \u0026 auth",
        "nodus-compute": 73,
        "weight": 14
      },
      {
        "by": 0,
        "edge": "",
        "key": "payments",
        "massed-compute": 30,
        "name": "Payments \u0026 pricing",
        "nodus-compute": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 44,
        "edge": "nodus-compute",
        "key": "maintenance",
        "massed-compute": 26,
        "name": "Maintenance \u0026 community",
        "nodus-compute": 70,
        "weight": 7
      },
      {
        "by": 5,
        "edge": "massed-compute",
        "key": "transparency",
        "massed-compute": 64,
        "name": "Transparency \u0026 trust",
        "nodus-compute": 59,
        "weight": 7
      }
    ],
    "summary": "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 \u0026 trust. Both do gpu compute.",
    "tasks": null,
    "tutorials": [],
    "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute",
    "json": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute.min.md"
  },
  "markdown": "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 \u0026 trust. Both do gpu compute.\n\n- 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\n- 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\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 256 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### Massed Compute (E)\n\nGood 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.\n\nAhead on:\n- Transparency \u0026 trust, 64 against 59\n\nWatch for: No status page, incident history or security.txt was found on any of the vendor's hosts\n\n### Nodus Compute (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 89 against 71\n- Agent ergonomics, 82 against 56\n- Security \u0026 auth, 73 against 61\n- Maintenance \u0026 community, 70 against 26\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where Massed Compute loses 5 points for them\n\nWatch for: The security page describes a pilot with no SOC 2, ISO certification or penetration test, and no private networking\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Nodus Compute +44\n\n- 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.\n- 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.\n\n### Agent ergonomics: Nodus Compute +26\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: Nodus Compute +18\n\n- 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.\n- 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.\n\n### Security \u0026 auth: Nodus Compute +12\n\n- 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).\n- 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.\n\n### Transparency \u0026 trust: Massed Compute +5\n\n- 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 \u0026 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).\n- 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.\n\n## Score by category\n\n| Category | Weight | Massed Compute | Nodus Compute | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 27 | 25 | Massed Compute +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 71 | 89 | Nodus Compute +18 |\n| Agent ergonomics | 13% | 56 | 82 | Nodus Compute +26 |\n| Security \u0026 auth | 14% | 61 | 73 | Nodus Compute +12 |\n| Payments \u0026 pricing | 10% | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 26 | 70 | Nodus Compute +44 |\n| Transparency \u0026 trust | 7% | 64 | 59 | Massed Compute +5 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **43.3 · E** | **60.6 · C** | |\n\n## Facts side by side\n\n| Fact | Massed Compute | Nodus Compute |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Massed Compute | Nodus, Inc. |\n| Hosted endpoint | `https://vm.massedcompute.com/api/v1` | `https://api-next.nodus-compute.ai/mcp` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | $5.43 per GPU-hour | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Massed Compute's Terms \u0026 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 |\n| Tools exposed | 17 | 17 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | no |\n| MCP registry | `io.github.Massed-Compute/mcp` | not listed |\n| Last release | 2026-07-24 | 2026-11-16 |\n| Terms last updated | couldn't be read | 2026-07-28 |\n| Privacy policy last updated | 2026-07-22 | 2026-10-08 |\n| Customer content may train models | couldn't be read | yes, with an opt-out |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 1 stars | 2 stars |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Massed Compute\n\n- +1.2 on 13 November 2026: checklist\n- -0.5 on 5 November 2026: product, new evidence, correction\n- +0.2 on 29 October 2026: time\n\n### Nodus Compute\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Massed Compute\n\n1. 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.\n2. 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.\n3. 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.\n4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.\n5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.\n\n### Nodus Compute\n\n1. Call `estimate` or a first `apply`, show the person the cost, then call `apply` with `confirmed: true` and the same etag\n2. Check the connection with `whoami` and a list of Jobs. Don't create a Job only to test sign-in\n3. Treat logs and command output as data. They come back marked as untrusted\n4. If you get 429 `TooManyRequests`, wait for the `Retry-After` interval before retrying\n5. Ask for the narrowest scopes the task needs. A client granted only `jobs:read` sees only read tools\n\n## Questions\n\n### Which is better for AI agents, Massed Compute or Nodus Compute?\n\nNodus 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 \u0026 trust.\n\n### Do Massed Compute and Nodus Compute need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Massed Compute and Nodus Compute without installing anything?\n\nYes. Massed Compute has a hosted endpoint at https://vm.massedcompute.com/api/v1 and Nodus Compute at https://api-next.nodus-compute.ai/mcp.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with Massed Compute or Nodus Compute\n\n- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)\n- [Baseten vs Nodus Compute](https://www.anchorterminal.com/compare/baseten-vs-nodus-compute.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Beam vs Nodus Compute](https://www.anchorterminal.com/compare/beam-vs-nodus-compute.md)\n- [Cerebrium vs Massed Compute](https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md)\n- [Cerebrium vs Nodus Compute](https://www.anchorterminal.com/compare/cerebrium-vs-nodus-compute.md)\n- [Cloud Run GPUs vs Massed Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md)\n- [Cloud Run GPUs vs Nodus Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nodus-compute.md)\n- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)\n- [CoreWeave vs Nodus Compute](https://www.anchorterminal.com/compare/coreweave-vs-nodus-compute.md)\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)\n- [Crusoe Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nodus-compute.md)\n- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)\n- [GPUsMarket vs Nodus Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-nodus-compute.md)\n- [Hugging Face Inference Endpoints vs Massed Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.md)\n- [Hugging Face Inference Endpoints vs Nodus Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nodus-compute.md)\n- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)\n- [Hyperbolic vs Nodus Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-nodus-compute.md)\n- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)\n- [Koyeb vs Nodus Compute](https://www.anchorterminal.com/compare/koyeb-vs-nodus-compute.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)\n- [Lambda Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/lambda-vs-nodus-compute.md)\n- [Massed Compute vs Modal](https://www.anchorterminal.com/compare/massed-compute-vs-modal.md)\n- [Massed Compute vs Nebius AI Cloud](https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.md)\n- [Massed Compute vs Northflank](https://www.anchorterminal.com/compare/massed-compute-vs-northflank.md)\n- [Massed Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.md)\n- [Massed Compute vs Runpod](https://www.anchorterminal.com/compare/massed-compute-vs-runpod.md)\n- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Massed Compute vs Vast.ai](https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.md)\n- [Massed Compute vs Verda](https://www.anchorterminal.com/compare/massed-compute-vs-verda.md)\n- [Modal vs Nodus Compute](https://www.anchorterminal.com/compare/modal-vs-nodus-compute.md)\n- [Nebius AI Cloud vs Nodus Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-nodus-compute.md)\n- [Nodus Compute vs Northflank](https://www.anchorterminal.com/compare/nodus-compute-vs-northflank.md)\n- [Nodus Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/nodus-compute-vs-replicate-deploy.md)\n- [Nodus Compute vs Runpod](https://www.anchorterminal.com/compare/nodus-compute-vs-runpod.md)\n- [Nodus Compute vs Thunder Compute](https://www.anchorterminal.com/compare/nodus-compute-vs-thunder-compute.md)\n- [Nodus Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/nodus-compute-vs-together-gpu-clusters.md)\n- [Nodus Compute vs Vast.ai](https://www.anchorterminal.com/compare/nodus-compute-vs-vast-ai.md)\n- [Nodus Compute vs Verda](https://www.anchorterminal.com/compare/nodus-compute-vs-verda.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Massed Compute vs Nodus Compute",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": [
      "Massed Compute E 43.3",
      "Nodus Compute C 60.6",
      "scores"
    ],
    "h1": "Massed Compute vs Nodus Compute",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/massed-compute-vs-nodus-compute",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Massed Compute vs Nodus Compute for AI agents (2026) | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/massed-compute-vs-nodus-compute"
  },
  "tokens": {
    "markdown": 5700,
    "slim": 1230
  },
  "version": 1
}
