# Render Sandboxes vs Sprites

> Sprites and Render Sandboxes score within a point of each other for code sandboxes, 68 and 67.5 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites
- Markdown: https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.md (~6,000 tokens)
- Slim: https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.min.md (~1,030 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.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

Sprites and Render Sandboxes score within a point of each other on agent readiness, 68 (B) and 67.5 (B). Render Sandboxes leads on schema & documentation, agent ergonomics, maintenance & community and transparency & trust. Both do code sandboxes.

- Render Sandboxes: grade B, 67.5/100, rank #441 of 1557. Markdown https://www.anchorterminal.com/tools/render-sandboxes.md · JSON https://www.anchorterminal.com/api/v1/tools/render-sandboxes.json
- Sprites: grade B, 68/100, rank #411 of 1557. Markdown https://www.anchorterminal.com/tools/sprites.md · JSON https://www.anchorterminal.com/api/v1/tools/sprites.json
- Best code execution sandboxes for AI agents: https://www.anchorterminal.com/best/code-sandboxes/index.md
- All 325 sandboxes comparisons: https://www.anchorterminal.com/compare/code-sandboxes/index.md

## Which one, for what

### Render Sandboxes (B)

Good for: Teams already on Render that want agent sandboxes beside their services, or anyone who needs long-running sandboxes with idle suspension and process snapshots.

Ahead on:
- Schema & documentation, 79 against 74
- Agent ergonomics, 73 against 68
- Maintenance & community, 85 against 80
- Transparency & trust, 80 against 66

Watch for: Public beta since 4 November 2026, with one region (Oregon) and no SLA outside Enterprise

### Sprites (B)

Good for: Agents that need a long-lived machine with installed tools and files kept between sessions, and rollback by checkpoint.

Ahead on:
- Reliability, 80 against 68
- Payments & pricing, 60 against 30

Watch for: Five partial Sprites incidents on the status page since 30 August 2026, including 7 hours 28 minutes of intermittent API failures on 23 September and 75 minutes of unreachable Sprite URLs on 11 October


## Why the edge

### Payments & pricing: Sprites +30

- Render Sandboxes (30): No x402, MPP or L402 (0). Per-unit prices published without login, $0.12 per CPU-hour used and $0.019 per GB-hour of memory, also given per minute and per second (30). No free sandbox allowance was found. Hobby workspaces cost $0 but sandbox compute is billed from the first second, and whether a payment method is needed first was not stated (0). A person signs up and creates the API key in the dashboard (0). 0+30+0+0 = 30.
- Sprites (60): No x402, MPP or L402 (0). Unit prices are public without a login, $0.0385 a CPU-hour, $0.021875 a GB-hour of memory, $0.000683 a GB-hour of hot storage and $0.000027 a GB-hour of cold storage (20). The product page and the pricing page now say every new user gets a $1 free trial with no credit card, invoices under $5 are waived, and new organisations get a $30 trial credit (20; was 10). A person signs up with a Fly.io account in a browser and creates the token (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

### Transparency & trust: Render Sandboxes +14

- Render Sandboxes (80): The service is closed, under terms last modified 10 July 2026. The SDKs are open source (MIT and Apache-2.0) (20 of 30). A privacy policy and DPA, plus stated lifetimes for sandbox data. The filesystem is deleted on termination, suspended sandboxes stay resumable 30 days, and snapshots expire 30 days after last use unless the TTL is changed (20 of 30). The docs warn that APIs, defaults and limits might change during the beta, and the SDK changelog marks breaking changes with migration steps, but no deprecation policy or notice period was found (8 of 20). Eight sub-processors with countries on render.com/security, and the region (Oregon) is stated (15 of 20). 20+20+8+15 = 63.
- Sprites (66): The SDKs are MIT and the platform is closed under terms of service effective 29 April 2026 (18). The privacy statement, effective 24 September 2026, keeps account data while the account is active and analytics data for at most 12 months. A pre-signed DPA is available on request. The terms grant Fly.io a licence to use customer data to run and improve the services. No retention period for Sprite data after deletion was found beyond the docs calling destruction permanent (18). No deprecation policy was found. The maintenance page says Sprites on Ubuntu 25.04 must upgrade, without a date (3). A sub-processor list of 34 vendors with countries and a dated change log, last updated 24 September 2026, names Tigris for Sprites object storage. The docs do not say which region a Sprite runs in (15). The four SDKs send coarse client-signal headers (interactive, CI or agent detection) by default; their READMEs disclose this and give the `SPRITES_CLIENT_SIGNALS=0` opt-out, so no deduction. 18 + 18 + 3 + 15 = 54.

### Reliability: Sprites +12

- Render Sandboxes (68): Scored on the hosted checklist, since sandboxes run on Render's infrastructure and the SDKs and CLI are clients of its API, the reading given to modal-sandboxes and vercel-sandbox. status.render.com is a Statuspage with incident history, though it has no Sandboxes component (20). Its history feed, read on 18 November 2026, has no incident naming sandboxes. Since the 4 November beta it lists API performance issues on 11 November for 18 minutes (13:17 to 13:35 UTC, dashboard and API requests) and a maintenance window announced on 10 November, with the REST API down for up to 30 minutes on 18 November. Earlier in the 90 days, builds and deploys did not start in any region on 14 October. Minor for this surface (20). Rate limits per operation with numbers, such as 100 creates and 1,000 execs a minute per user, and per-group concurrency caps (15). The docs say limits return 429, and the API schema in the SDK source documents `Retry-After` and `RateLimit-*` headers, but there is no backoff guidance in the sandbox docs and no idempotency key on create (8 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing their terms (5 of 10). Public beta, not generally available (0). 20+20+15+8+5+0 = 68.
- Sprites (80): Hosted lines. status.flyio.net runs on incident.io with history and a Sprites component (20). Five Sprites incidents since 6 August, each partial in its own text, so minor under this run's reading. Deletion jobs failed for 47 minutes on 30 August, "a subset of Sprites users" had API errors for 1 hour 38 minutes on 2 September, intermittent API failures starting near SJC ran 7 hours 28 minutes on 23 September, creates failed in regions outside Europe for 28 minutes on 8 October, and "some or all" Sprite URLs on sprites.app were unavailable for about 75 minutes on 11 October after a certificate error (20; was 5, which isn't a checklist value). The product page gives creation limits of 10 a minute on pay-as-you-go and 60 to 240 on plans, and 100 running Sprites on the Hero plan. No general request limits were found in the docs (10). The docs and the OpenAPI document list no 429 response and no idempotency keys; the Go SDK reads `Retry-After` and `X-RateLimit` headers on a 429 and names a `sprite_creation_rate_limited` code, so Retry-After handling alone (10; was 7). Fly.io's published Service Level Agreement applies to the Services for customers on an Enterprise plan, with 99.9 per cent monthly availability and service credits of 10 to 30 per cent, and excludes no product, so it is read as covering Sprites (10; was 5, which isn't a checklist value). No beta or preview label was found on Sprites, so the surface is read as generally available, though the API document is version 0.1.12 and the SDKs are 0.x (10; was 8, which isn't a checklist value). 20 + 20 + 10 + 10 + 10 + 10 = 80.

### Schema & documentation: Render Sandboxes +5

- Render Sandboxes (79): No public REST API or OpenAPI document for sandboxes, and the SDK README lists the REST API as "Soon". The SDKs are typed and generated from Render's API schema, and the TypeScript and Python references document every method, which we count as 15 of 25 for an SDK, the reading modal-sandboxes was given (15). render.com/llms.txt, a Markdown twin of every page and a single sandboxes bundle at /docs/sandboxes/all (10). The guides say when to use idle suspension, runtime timeouts, filesystem or process snapshots and sandbox groups, and what a deleted snapshot breaks (15). Typed SDK inputs with a plan enum, a network policy type and documented bounds such as a 64-character snapshot name (12). Examples in CLI, TypeScript and both Python styles on every page, and 18 named error types with when each is thrown. No list of API error codes (14). Semver SDK changelog with dates and Render's product changelog. The 1.9.0 breaking change came in a minor version, called out in the changelog (13). 15+10+15+12+14+13 = 79.
- Sprites (74): A public OpenAPI 3.1 document with 44 operations and 59 schemas, plus an AsyncAPI file for the WebSocket calls (25). llms.txt and a Markdown copy of every docs page (10). Concept pages say when to use Services, Tasks and checkpoints and when not to, while operation descriptions are one line each (15). Request bodies have required fields and examples, but the document has 6 enums and no schema for error bodies (10). 116 examples in the OpenAPI document. Error responses are a status code and a short phrase, and the product page's create and exec examples disagree with the OpenAPI document (8). Paths are versioned under `/v1`. No API changelog was found, and only the Python SDK keeps a changelog file (6).

### Agent ergonomics: Render Sandboxes +5

- Render Sandboxes (73): Downloads take `maxSizeBytes` (256 MiB default since 1.8.0), exec streams output as events, and lists take a limit (15). `list` filters by status and name with cursor pagination, and snapshots and images list by name and status (18). Typed errors for each known API code since 1.9.0, such as `SandboxGroupSuspendedError` and `SandboxEndedError` with the sandbox's status, and 429 for both rate and concurrency caps. A nonzero exit code does not raise, which the docs state (17). No idempotency key for creating sandboxes or snapshots. The CLI previews stop and delete without `--confirm` (8 of 20). Sensible defaults (`1c-2g`, the default group) with few required parameters, SDKs in TypeScript, Python and Go plus the CLI (15). 15+18+17+8+15 = 73.
- Sprites (68): List calls take `max_results`, and service logs take `lines` and `duration`. Exec returns command output directly, with a WebSocket route for streaming (17). Sprite lists page with `continuation_token` and filter by `prefix` (16). Status codes are listed per operation and the SDKs raise typed errors with a machine code, but no code list is published (10). No idempotency keys. Service creation is a PUT by name and Sprite names are unique per organisation, and the hosted MCP server marks tools as read-only or destructive (10). Creating a Sprite needs only a name, and there are official SDKs in four languages and a CLI (15).

### Maintenance & community: Render Sandboxes +5

- Render Sandboxes (85): SDK 1.9.0 on 16 November 2026 (30). Eight SDK releases in the 90 days, from 1.1.0 on 10 September to 1.9.0, five of them since 17 October (20). 118 commits since 18 October from Render staff and release bots, the last on 18 November. Two open pull requests. The issue list draws in a script and could not be read, so responsiveness is not established (10 of 25). Official SDKs in TypeScript, Python and Go, current with the docs (15). CI for both languages with pinned actions, Dependabot configured. The result of the latest run was not seen (10). 30+20+10+15+10 = 85.
- Sprites (80): `@fly/sprites` v0.2.4 and `sprites-go` v0.2.2 on 20 October 2026, 15 days ago, each with a code fix (HTTP exec exit frames; directory stat and connection diagnostics) (30). Since 6 August, tags v0.2.1 to v0.2.4 of the JavaScript SDK, v0.5.1 to v0.7.2 of `sprites-py`, v0.1.1 to v0.2.2 of the Go SDK and v0.2.1 to v0.2.4 of the Elixir SDK, many more than three even at half (20). No product changelog was found. Support is the community forum below the Hero plan and email above it. Issue response on GitHub was not read (7). Current official SDKs for JavaScript, Go, Python and Elixir (15). All four SDK repositories run a checks workflow in CI and take dependency updates. The JavaScript SDK requires Node.js 24 or later (8). 30 + 20 + 7 + 15 + 8 = 80.

## Score by category

| Category | Weight | Render Sandboxes | Sprites | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 68 | 80 | Sprites +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 74 | Render Sandboxes +5 |
| Agent ergonomics | 13% | 73 | 68 | Render Sandboxes +5 |
| Security & auth | 14% | 63 | 61 | Render Sandboxes +2 |
| Payments & pricing | 10% | 30 | 60 | Sprites +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 80 | Render Sandboxes +5 |
| Transparency & trust | 7% | 80 | 66 | Render Sandboxes +14 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **67.5 · B** | **68 · B** | |

## Facts side by side

| Fact | Render Sandboxes | Sprites |
| --- | --- | --- |
| Kind | SDK + MCP | HTTP API |
| Vendor | Render Services, Inc. | Fly.io |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | The service is proprietary under Render's terms. The SDK is MIT (TypeScript `@renderinc/sdk`) and Apache-2.0 (Python `render`) | Proprietary service under the Fly.io Terms of Service. The JavaScript, Go, Python and Elixir SDKs are MIT |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-16 | 2026-10-20 |
| Terms last updated | 2026-07-10 | 2026-04-29 |
| Privacy policy last updated | 2026-07-10 | 2026-09-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 27 stars | 158k npm/wk, 59k PyPI/wk |

## How the scores have moved

### Render Sandboxes

No score change since it was listed.

### Sprites

- +2.5 on 13 November 2026: checklist
- +6.9 on 4 November 2026 (C to B): security, new evidence, correction
- +0.3 on 27 October 2026: checklist

## Verdicts

**Render Sandboxes.** Render Sandboxes has per-operation rate limits, per-second prices and typed SDKs in three languages, with sandboxes that suspend when idle and resume from snapshots. It is a public beta in one region, with no public REST API, no idempotency on create and API keys that reach every workspace.

**Sprites.** A Sprite keeps a 100 GB ext4 disk between runs, bills compute only while active and can be checkpointed and restored through a published OpenAPI contract. The status page records five partial Sprites incidents since August, one lasting over seven hours, and outbound network access is unrestricted until a policy is set.

## Before you call either

### Render Sandboxes

1. Set `timeoutSeconds` when you create a sandbox. A disabled timeout keeps the sandbox, and its billing, running until you terminate it
2. Pass `networkPolicy` with an allowlist or deny-all at creation, since the default allows outbound traffic to any destination
3. Check the exit event's `exit_code` after `exec`. A nonzero exit code does not raise an error in the SDK
4. If create returns 429, check whether the group is at its concurrency cap before you retry. Rate and concurrency limits share the same code
5. Use `ttlSeconds` on snapshots with SDK 1.9.0 or later. The `expiresAt` option was removed in 1.9.0

### Sprites

1. Create a token at sprites.dev/account after a browser signup, and send it as `Authorization: Bearer <token>` to `https://api.sprites.dev`
2. Follow the OpenAPI document, not the product page example. Create with `POST /v1/sprites` and a JSON `name`, and run commands with `POST /v1/sprites/{name}/exec` using `cmd` query parameters
3. Set a network policy with `POST /v1/sprites/{name}/policy/network` before running untrusted code. Egress is open until one is set
4. Processes started by exec stop on a cold wake. Define a Service for anything that must answer the request that wakes the Sprite
5. Create a checkpoint before a restore. Restoring replaces the filesystem, ends active sessions and keeps no copy of the replaced state
6. Sprite creation is limited to 10 a minute on pay-as-you-go. The Go SDK reads `Retry-After` and the error code `sprite_creation_rate_limited` on a 429
7. Delete Sprites you no longer need. An idle Sprite still bills cold storage for the bytes it holds
8. Set `SPRITES_CLIENT_SIGNALS=0` before the first SDK call if your operator doesn't want client-signal headers sent

## Questions

### Which is better for AI agents, Render Sandboxes or Sprites?

Sprites and Render Sandboxes score within a point of each other on agent readiness, 68 (B) and 67.5 (B). Render Sandboxes leads on schema & documentation, agent ergonomics, maintenance & community and transparency & trust.

### Can an agent call Render Sandboxes and Sprites without installing anything?

No hosted endpoint is listed for Render Sandboxes. No hosted endpoint is listed for Sprites.


## For agents

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

## Other comparisons with Render Sandboxes or Sprites

- [Amazon Bedrock AgentCore Code Interpreter vs Render Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-render-sandboxes.md)
- [Amazon Bedrock AgentCore Code Interpreter vs Sprites](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites.md)
- [Blaxel Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-render-sandboxes.md)
- [Blaxel Sandboxes vs Sprites](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-sprites.md)
- [boat vs Render Sandboxes](https://www.anchorterminal.com/compare/boat-vs-render-sandboxes.md)
- [boat vs Sprites](https://www.anchorterminal.com/compare/boat-vs-sprites.md)
- [Celesto (formerly SmolVM) vs Render Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-render-sandboxes.md)
- [Celesto (formerly SmolVM) vs Sprites](https://www.anchorterminal.com/compare/celesto-vs-sprites.md)
- [Cloudflare Sandbox SDK vs Render Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-render-sandboxes.md)
- [Cloudflare Sandbox SDK vs Sprites](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-sprites.md)
- [Daytona vs Render Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-render-sandboxes.md)
- [Daytona vs Sprites](https://www.anchorterminal.com/compare/daytona-vs-sprites.md)
- [Deno Sandbox vs Render Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-render-sandboxes.md)
- [Deno Sandbox vs Sprites](https://www.anchorterminal.com/compare/deno-sandbox-vs-sprites.md)
- [DigitalOcean Managed Agents vs Render Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-render-sandboxes.md)
- [DigitalOcean Managed Agents vs Sprites](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites.md)
- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)
- [Docker Sandboxes vs Sprites](https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.md)
- [E2B vs Render Sandboxes](https://www.anchorterminal.com/compare/e2b-vs-render-sandboxes.md)
- [E2B vs Sprites](https://www.anchorterminal.com/compare/e2b-vs-sprites.md)
- [Freestyle vs Render Sandboxes](https://www.anchorterminal.com/compare/freestyle-vs-render-sandboxes.md)
- [Freestyle vs Sprites](https://www.anchorterminal.com/compare/freestyle-vs-sprites.md)
- [InstaVM vs Render Sandboxes](https://www.anchorterminal.com/compare/instavm-vs-render-sandboxes.md)
- [InstaVM vs Sprites](https://www.anchorterminal.com/compare/instavm-vs-sprites.md)
- [Maritime vs Render Sandboxes](https://www.anchorterminal.com/compare/maritime-vs-render-sandboxes.md)
- [Maritime vs Sprites](https://www.anchorterminal.com/compare/maritime-vs-sprites.md)
- [Microsoft Execution Containers vs Render Sandboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-render-sandboxes.md)
- [Microsoft Execution Containers vs Sprites](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.md)
- [Modal Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/modal-sandboxes-vs-render-sandboxes.md)
- [Modal Sandboxes vs Sprites](https://www.anchorterminal.com/compare/modal-sandboxes-vs-sprites.md)
- [Morph Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/morph-cloud-vs-render-sandboxes.md)
- [Morph Cloud vs Sprites](https://www.anchorterminal.com/compare/morph-cloud-vs-sprites.md)
- [Offscreen vs Render Sandboxes](https://www.anchorterminal.com/compare/offscreen-vs-render-sandboxes.md)
- [Offscreen vs Sprites](https://www.anchorterminal.com/compare/offscreen-vs-sprites.md)
- [SPACE vs Render Sandboxes](https://www.anchorterminal.com/compare/perplexity-space-vs-render-sandboxes.md)
- [SPACE vs Sprites](https://www.anchorterminal.com/compare/perplexity-space-vs-sprites.md)
- [Render Sandboxes vs Runloop Devboxes](https://www.anchorterminal.com/compare/render-sandboxes-vs-runloop.md)
- [Render Sandboxes vs Sandbox0](https://www.anchorterminal.com/compare/render-sandboxes-vs-sandbox0.md)
- [Render Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-together-code-sandbox.md)
- [Render Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/render-sandboxes-vs-vercel-sandbox.md)
- [Runloop Devboxes vs Sprites](https://www.anchorterminal.com/compare/runloop-vs-sprites.md)
- [Sandbox0 vs Sprites](https://www.anchorterminal.com/compare/sandbox0-vs-sprites.md)
- [Sprites vs Together Code Sandbox](https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox.md)
- [Sprites vs Vercel Sandbox](https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox.md)
- [Agent 37 Cloud vs Render Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-render-sandboxes.md)
- [Agent 37 Cloud vs Sprites](https://www.anchorterminal.com/compare/agent37-vs-sprites.md)
- [DeltaBox Lite vs Render Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-render-sandboxes.md)
- [DeltaBox Lite vs Sprites](https://www.anchorterminal.com/compare/deltabox-lite-vs-sprites.md)

---

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