lean-plugin
Related Servers
Alternatives to lean-plugin
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables 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.289 PyPI7MIT- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query locally installed language servers over stdio MCP for read-only code intelligence, including definitions, references, implementations, hover types, symbols, and diagnostics.9 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to perform sandboxed file reads, writes, and listing, inspect credential-masked environment variables, check git status, and execute commands with strict timeouts over a clean stdio JSON-RPC channel.MIT
- AlicenseNot gradedqualityDmaintenanceEnables verification of Lean 4 mathematical proofs via MCP tools, allowing AI clients to compile and check theorems with Mathlib.2MIT
- AlicenseBqualityBmaintenanceExposes a native JSON-RPC 2.0 stdio MCP server that lets autonomous coding agents self-verify before finishing a turn, catching broken syntax, mutated public signatures, out-of-scope edits, banned imports, and deleted test assertions via deterministic static AST checks against a SHA-256 baseline. It enables zero-token spec validation, drift detection, checkpointing, and atomic rollback of broken agent mutations.51MIT
- AlicenseNot gradedqualityBmaintenanceServes five offline diagnostic tools over stdio that let an agent scan a repository for AI context noise, trace why a CLI command is missing, measure whether a build cache actually pays off, and rank flaky or always-failing tests from JUnit runs. Each tool returns the same JSON as the CLI, and an optional sandbox root keeps all path access confined to one repo.570 npmApache 2.0
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: lean_diagnostics elaborates a specific source file, while lean_verify runs package-level proof verification. An agent can easily choose between them based on whether it needs file diagnostics or target verification.
Both tools use the same lean_ prefix and snake_case style, which is predictable. The only minor inconsistency is grammatical form: diagnostics is a noun while verify is a verb, but the pattern remains readable.
Two tools is thin for a Lean plugin, even a narrowly scoped one. It covers the two core operations but leaves little room for related workflows, making the count borderline.
The surface covers file elaboration and package verification, but notable gaps remain: no build/clean, no listing or reading files, and no way to verify a specific non-default target. Agents may be able to work around some of these, but the lifecycle is incomplete.