Free vs paid code execution servers you're pricing isolation, not CPU.
Running agent-generated code is cheap. Running it safely is not. The free-versus-paid line in code execution tracks how much isolation stands between the agent's code and everything you care about.
Code execution is the category where the worst case isn't a wrong answer — it's a compromised host. An agent that can run arbitrary code can also exfiltrate environment variables, scan your network, or fill your disk. Every server here is, at bottom, an answer to the question "how contained is the blast?"
The free options answer it with your own infrastructure: runno's sandbox, podman-mcp-server's containers, Shell Exec's bare bash access. The paid logic in this category is about renting isolation — and sometimes hardware — that you'd rather not own.
Code Execution MCP servers on the Loomal Index
runno
MCP Server for the Runno Sandbox
code-runner
Code Runner MCP Server which can run code in various programming languages.
cesium-mcp-runtime
AI-powered 3D globe control via MCP. Camera, layers, markers, spatial analysis with CesiumJS.
podman-mcp-server
A Model Context Protocol (MCP) server for container runtimes (Podman and Docker)
Qiskit IBM Runtime MCP Server
MCP server for IBM Quantum computing services through Qiskit IBM Runtime
build123d MCP
AI-driven 3D CAD via build123d: execute, render, measure, and export geometry interactively.
glassbox-framework
Runtime constitutional verification for AI answers — claim reasoning, ECS, red team, audits.
RLM Tools
Persistent Python sandbox for token-efficient codebase exploration in MCP clients
mcp-server-colab-exec
Execute Python code on Google Colab GPU runtimes (T4/L4) from any MCP client
Vaara
EU AI Act runtime evidence proxy for MCP servers: gating, tamper-evident audit, time anchor
Vaara MCP Server
EU AI Act runtime evidence as a standalone MCP server: gating, tamper-evident audit
Shell Exec
Execute bash commands with background job support.
Showing 12 of 33 live Code Execution servers — browse them all on the marketplace.
The free spectrum runs from bare to boxed
Free execution servers differ mostly in how much they trust the code. Shell Exec runs bash on the host directly — maximal power, zero containment, appropriate only when the agent and machine are both yours. podman-mcp-server interposes containers via Podman or Docker. runno wraps execution in a purpose-built sandbox, and RLM Tools keeps a persistent Python session for codebase exploration. Same category, very different failure modes.
All of them are free to run because they execute on compute you already have. The cost is the engineering judgment of matching containment level to how much you trust what the agent writes.
What self-hosted isolation actually costs
Real isolation has real overhead: keeping container runtimes patched, setting CPU, memory, and disk quotas so a runaway loop can't take the host down, scrubbing network access, and resetting state between runs so one execution can't poison the next. For multi-tenant setups — several agents, or agents acting for users you don't know — the bar rises to VM-level isolation, and the maintenance becomes a standing job.
Special hardware raises it further. mcp-server-colab-exec exists because GPU execution is its own provisioning problem: T4s and L4s aren't sitting under most desks.
Paying per execution with x402
A hosted execution endpoint sells the finished article: an isolated environment that exists for one run and is destroyed after. With x402 pricing, an agent buys it in-band — 402 Payment Required, price paid in USDC on Base, settlement in about two seconds, Ed25519-signed receipt, and the code runs only after payment clears. From $0.01 per call, with no account or API key to provision.
Per-execution is the honest unit here because executions are spiky and unequal: a hundred quick syntax checks one day, one GPU-hungry batch job the next. Paying per run prices each correctly; a subscription prices for the peak and idles the rest of the month.
Trust decides, then volume
Decide on trust first. Code written by your own agent against your own repo can run in a free local sandbox like runno or a container via podman-mcp-server. Code from agents or users you don't control needs isolation strong enough that you should ask whether you want to operate it at all — that's the paid endpoint's case. Then let volume tune the answer: constant heavy execution may justify owning infrastructure; intermittent execution almost never does.
If you already operate hardened sandboxes or GPU runners, that capability is sellable per run. Claim your listing on Loomal and price above your per-execution cost; the 5% fee on settled transactions is currently waived.
Frequently asked questions
Should my agent use a free or paid code execution server?
Trust is the deciding variable. Your own agent's code against your own machine runs fine in a free sandbox like runno or a Podman container. Untrusted or third-party code wants stronger isolation than most teams should operate themselves, and a paid per-execution endpoint moves that burden — and its failure modes — to a specialist.
Why pay per execution instead of subscribing to a sandbox service?
Execution demand is lumpy: bursts of test runs, then silence, then one large job. x402 per-execution pricing bills exactly that shape, settled in USDC at call time with no signup, while a subscription charges for capacity you mostly don't use. High, steady execution volume is the one case where a flat plan wins.
Does paying for execution make it more secure?
Not by itself — security comes from the operator's isolation architecture, not the invoice. What payment changes is incentive and accountability: a per-call operator's revenue depends on containment working, and every run carries a signed receipt. You should still ask any endpoint, free or paid, how environments are isolated and destroyed.
Where can I compare code execution MCP servers?
Loomal's Code Execution category page lists the live servers — bare shell access, container runtimes, sandboxes, and GPU bridges — with descriptions, package details, and x402 per-call prices wherever maintainers have claimed and priced their listings.
Run a Code Execution MCP server?
Claim your listing, set a per-call USDC price, and let AI agents pay for every call over x402.
List it on Loomal