Tokenized Stock vs Container Use

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

Tokenized Stock logoTokenized StockCode Execution · Local subprocess (stdio)Buy/sell tokenized US stocks (Dinari dShares) in USDC. Daily USD cap guard. Sandbox default.39FairAuth: not declaredContainer 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 required

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

Which MCP server should you choose?

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTokenized Stock logoTokenized StockContainer Use logoContainer Use
CategoryCode ExecutionCode Execution
Quality signal39/100 · Fair51/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars34,079
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Tokenized Stock tools

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

Container Use 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.

Tokenized Stock

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

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.

Frequently asked questions

Tokenized Stock is categorized under Code Execution and uses a local stdio subprocess. Container Use belongs to Code Execution and uses an install path we have not confirmed yet. Pick Tokenized Stock for code execution work and Container Use 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.

Tokenized Stock has no declared pricing — check the project's own site. Container Use is listed as free. Auth: no auth required. 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 tokenized-stock and dagger-container-use as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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