Container Use vs Prover
A side-by-side look at the Container Use and Prover MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Container Use for code execution work; choose Prover for code execution over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Container Use when
- You need dedicated capabilities in the Code Execution domain.
- Its auth model fits you: No auth required.
Choose Prover when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
lean4_build, lean4_prove_theorems, lean4_get_job_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 51/100 · Good | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,079 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Container Use | View Prover |
Tools & capabilities
Container Use tools
No tool names declared yet. Check the project README from the listing page.
Prover tools 3
lean4_buildCompile Lean 4 source code in a Mathlib-enabled sandbox. Code is sent to external cloud services for compilation; if proving, also for AI processing.lean4_prove_theoremsAutomatically prove Lean 4 theorems that contain `sorry`. Code is sent to external cloud services for compilation and AI proving.lean4_get_job_statusPoll for the status and result of any ax-prover job.
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.
Prover
{
"mcpServers": {
"prover": {
"url": "https://prover.axiomatic-ai.com/mcp/"
}
}
}
Frequently asked questions
Container Use is categorized under Code Execution and uses an install path we have not confirmed yet. Prover belongs to Code Execution and uses a remote HTTP/SSE transport. Pick Container Use for code execution work and Prover 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. Prover has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 prover 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,079 GitHub stars. Prover has 60/100 (Good) with 0 views, 0 installs and 0 GitHub stars.