Log inSubmit server

MuPag Sandbox Payments vs MCP Run Python

A side-by-side look at the MuPag Sandbox Payments 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.

M
MuPag Sandbox PaymentsCode ExecutionSandbox-only MuPag MCP server for approved payments, subscriptions, refunds, and reconciliation.37FairAuth: not declaredMCP Run Python logoMCP Run PythonCode ExecutionRun Python code in a secure sandbox via MCP tool calls43FairAuth: no auth required

Verdict: choose MuPag Sandbox Payments for code execution work; 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?

M
Choose MuPag Sandbox Payments when

  • You need dedicated capabilities in the Code Execution domain.
Explore MuPag Sandbox Payments

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.

Spec
M
MuPag Sandbox Payments		MCP Run Python logoMCP Run Python
CategoryCode ExecutionCode Execution
Quality signal37/100 · Fair43/100 · Fair
Install commandNot confirmed yetNot confirmed yet
Transport——
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—20,797
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView MuPag Sandbox Payments View MCP Run Python

Tools & capabilities

MuPag Sandbox Payments 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.

MuPag Sandbox Payments

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

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

MuPag Sandbox Payments is categorized under Code Execution and uses an install path we have not confirmed yet. MCP Run Python belongs to Code Execution and uses an install path we have not confirmed yet. Pick MuPag Sandbox Payments for code execution work and MCP Run Python for code execution.

Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.

MuPag Sandbox Payments 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 mupag-sandbox-payments 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, MuPag Sandbox Payments has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Run Python has 43/100 (Fair) with 2 views, 0 installs and 20,797 GitHub stars.

Popular comparisons with MuPag Sandbox Payments

Popular comparisons with MCP Run Python