Skip to main content
Glama

Related Servers

Alternatives to Proof-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to perform Lean 4 formal verification, navigate project symbols offline, and inspect C FFI bindings.
      5
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-driven formal proof search in Lean 4 by submitting theorems with sorry placeholders and running parallel LLM agents whose proposed edits are verified by the Lean compiler until a machine-checked proof is produced. Also provides Mathlib theorem search and job/attempt management tools.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to develop Rocq proofs by checking files for diagnostics across proofs and running commands at specific positions for queries and debugging. It integrates with Rocq LSP and project configuration to support interactive proof workflows.
      2
      145 PyPI
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables LLM agents to interact with the Lean theorem prover through the Language Server Protocol, providing tools for analyzing Lean projects, accessing diagnostics, goal states, documentation, and searching for theorems using both local and external search services.
      22
      81,428 PyPI
      559
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code, Codex and Cursor to check and verify Lean 4 proofs, inspect goals at a position, try tactics, list holes, and extract declarations against hosted Lean releases with pinned libraries. Edits are checked on warm remote workers that reuse Lean's work between calls, so agents can iterate on proofs against their intended statements.
      188 PyPI
      7
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct roles across discovery, preparation, execution, and verification. The main overlap is between proof_verify_workspace and proof_check_generated, and between proof_discover_qa and proof_prepare_verification, but descriptions clarify their boundaries.

    Naming Consistency5/5

    All tools use a consistent proof_<verb>_<object> pattern, such as proof_check_lean, proof_run_python_test, and proof_verify_workspace. The shared prefix and verb-noun structure make the set predictable.

    Tool Count5/5

    Eight tools is well-scoped for a verification workflow covering discovery, preparation, checking, and approved execution. Each tool has a distinct stage or artifact type, with no obvious padding.

    Completeness4/5

    The surface covers the main lifecycle from QA discovery through Lean/TLA+ checks and generated artifact verification. Minor gaps exist around inspecting prior results or managing .proof-mcp.json artifacts, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data