Skip to main content
Glama
gleachkr

Aristotle MCP Server

by gleachkr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Aristotle MCP Server

No user-submitted related servers found.

    Related Servers

    • axle-mcp

      Vilin97
      F
      license
      Not graded
      quality
      D
      maintenance
      Integrates the AXLE (Axiom Lean Engine) CLI with AI assistants to provide comprehensive tools for Lean 4 proof engineering. It enables users to validate, repair, and transform Lean theorems through a remote API without requiring a local Lean installation.
      2
      -

    • Formath MCP

      yutayamamoto
      F
      license
      B
      quality
      Not graded
      maintenance
      Enables extraction of mathematical content from TeX papers and conversion to Lean code through a structured intermediate representation. Supports project scaffolding, entity management, and task tracking for mathematical formalization workflows.
      14
      -

    • Lean LSP MCP

      oOo0oOo
      A
      license
      A
      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.
      23
      158,138 PyPI
      503
      MIT

    • leanscreen

      ibrahimmian36
      F
      license
      A
      quality
      B
      maintenance
      A calibrated faithfulness screen for informal↔Lean 4 statement pairs, served over MCP. It provides deterministic checks and deep LLM-based analysis to help draft Lean statements.
      2
      6
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 6 tools

    Disambiguation2/5

    There is significant overlap between prove_informal, prove_informal_text, prove_lean_code, and prove_lean_file, as all four handle proof submission with only minor input format differences. This creates ambiguity for an agent trying to select the right tool, especially between the informal text and file variants. The get_project_status and list_recent_projects are distinct, but the core proving tools are poorly differentiated.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern throughout, which is good. However, there is a minor inconsistency: most tools use verb_noun (e.g., get_project_status, prove_informal), but list_recent_projects uses verb_adjective_noun, which slightly deviates from the pattern. Overall, the naming is mostly predictable and readable.

    Tool Count4/5

    With 6 tools, the count is reasonable for a server focused on mathematical proof automation. It covers key operations like project listing, status checking, and proof submission. However, the set feels slightly thin as it lacks tools for managing or updating existing projects, but it is well-scoped for the core workflow.

    Completeness3/5

    The tool surface covers basic submission and status checking, but there are notable gaps. For example, there are no tools to update, cancel, or delete projects, and no way to retrieve proof results beyond status. This could lead to dead ends for agents needing to manage project lifecycles, though core submission workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources