WBX Sandbox

cz.wbxPublished by wbx.czOfficial publisherv0.15.72Updated Nov 19, 2026

Isolated Linux microVMs for AI agents: run code and long jobs, share apps over HTTPS, resume later.

The publisher's own server: sandbox.co

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A remote MCP endpoint that gives AI agents Firecracker microVM sandboxes to run code, jobs and batches, with per-job cost caps.

What you can do
  • Run code inside isolated Firecracker microVM sandboxes provisioned for the agent.
  • Execute jobs and batch workloads in those sandboxes.
  • Apply a cost cap per job to limit spending on each run.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when an assistant needs an isolated, disposable machine to execute code or batch jobs rather than running them on the user's own machine, and when per-job spending limits matter.
Requirements
A remote streamable HTTP endpoint at the provider's sandbox host, with OAuth authentication required. No environment variables or headers are declared.
Before you install
OAuth access is required, so the assistant is granted a credentialed session to a third-party sandbox service. Jobs run code and may incur charges, bounded only by the per-job cost caps; review how caps and billing are configured before running workloads.

Installation

In SourceWeft

  1. Open WBX Sandbox in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cz.wbx%2Fsandbox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wbx-sandbox": {
      "type": "http",
      "url": "https://sandbox.wbx.cz/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.15.72LatestNov 19, 2026
  2. v0.15.70Nov 19, 2026
  3. v0.14.21Nov 11, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Sandbox integrations