Prover vs MCP Js
A side-by-side look at the Prover and MCP Js MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Prover for code execution work over a hosted endpoint; choose MCP Js 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 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.
Choose MCP Js when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
run_js, get_execution, get_execution_output.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 60/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 62 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View Prover | View MCP Js |
Tools & capabilities
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.
MCP Js tools 5
run_jsStateful: queue execution → `{execution_id}`. Stateless: run and return `{output, error?}`.get_executionPoll status/result of an execution.get_execution_outputRead paginated console output (line or byte).cancel_executionTerminate a running execution.list_executionsList executions and their status.
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.
Prover
{
"mcpServers": {
"prover": {
"url": "https://prover.axiomatic-ai.com/mcp/"
}
}
}
MCP Js
{
"mcpServers": {
"r33drichards-mcp-js": {
"url": "http://localhost:8080/mcp"
}
}
}
Frequently asked questions
Prover is categorized under Code Execution and uses a remote HTTP/SSE transport. MCP Js belongs to Code Execution and uses a remote HTTP/SSE transport. Pick Prover for code execution work and MCP Js 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.
Prover has no declared pricing — check the project's own site. Auth: oauth 2.0. MCP Js is listed as free. Auth: api key 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 prover and r33drichards-mcp-js as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Prover has a quality signal of 60/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Js has 59/100 (Good) with 3 views, 0 installs and 62 GitHub stars.