Container Use vs Tokenized Stock

A side-by-side look at the Container Use and Tokenized Stock MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Container Use logoContainer UseCode ExecutionContainerized environments for coding agents. Multiple agents can work independently, isolated in fresh containers and git branches. No conflicts, many experiments. Full execution history, terminal access to agent environments, git workflow. Any agent/model/infra stack.51GoodAuth: no auth requiredTokenized Stock logoTokenized StockCode Execution · Local subprocess (stdio)Buy/sell tokenized US stocks (Dinari dShares) in USDC. Daily USD cap guard. Sandbox default.39FairAuth: not declared

Verdict: choose Container Use for code execution work; choose Tokenized Stock for code execution as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Container Use logoChoose Container Use when

  • You need dedicated capabilities in the Code Execution domain.
  • Its auth model fits you: No auth required.
Explore Container Use

Tokenized Stock logoChoose Tokenized Stock when

  • You need dedicated capabilities in the Code Execution domain.
  • You prefer a local stdio subprocess transport.
Explore Tokenized Stock

Feature & specification comparison

Rows where the two servers differ are marked.

SpecContainer Use logoContainer UseTokenized Stock logoTokenized Stock
CategoryCode ExecutionCode Execution
Quality signal51/100 · Good39/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4,0783
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Container Use tools

No tool names declared yet. Check the project README from the listing page.

Tokenized Stock tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Container Use

No confirmed install command for Container Use yet — follow the setup steps linked from its listing page rather than a guessed package name.

Tokenized Stock

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tokenized-stock": {
      "command": "npx",
      "args": [
        "-y",
        "create-lemon-mcp"
      ]
    }
  }
}

Frequently asked questions

Container Use is categorized under Code Execution and uses an install path we have not confirmed yet. Tokenized Stock belongs to Code Execution and uses a local stdio subprocess. Pick Container Use for code execution work and Tokenized Stock for code execution.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Container Use has no confirmed install command yet — follow its own setup instructions.

Container Use is listed as free. Auth: no auth required. Tokenized Stock has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add dagger-container-use and tokenized-stock as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Container Use has a quality signal of 51/100 (Good) with 3 views, 0 installs and 4,078 GitHub stars. Tokenized Stock has 39/100 (Fair) with 2 views, 0 installs and 3 GitHub stars.