Tokenized Stock vs MCP Run Python

A side-by-side look at the Tokenized Stock and MCP Run Python 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 declaredMCP Run Python logoMCP Run PythonCode ExecutionRun Python code in a secure sandbox via MCP tool calls43FairAuth: no auth required

Verdict: choose Tokenized Stock for code execution work as a local process; choose MCP Run Python 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

MCP Run Python logoChoose MCP Run Python when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTokenized Stock logoTokenized StockMCP Run Python logoMCP Run Python
CategoryCode ExecutionCode Execution
Quality signal39/100 · Fair43/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars320,823
Directory activity 2 views 0 installs 0 upvotes 2 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.

MCP Run Python 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"
      ]
    }
  }
}

MCP Run Python

No confirmed install command for MCP Run Python 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. MCP Run Python belongs to Code Execution and uses an install path we have not confirmed yet. Pick Tokenized Stock for code execution work and MCP Run Python 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. MCP Run Python has no confirmed install command yet — follow its own setup instructions.

Tokenized Stock has no declared pricing — check the project's own site. MCP Run Python 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 pydantic-pydantic-ai-mcp-run-python 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. MCP Run Python has 43/100 (Fair) with 2 views, 0 installs and 20,823 GitHub stars.