Lean4 formal proof — Atom

org.aimldsPublished by aimlds.orgv0.1.0Updated Nov 15, 2026

Lean4 formal proof, delivered per API call as an atom service on Conduit Atoms.

The publisher's own server: Proof Holdings

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote Conduit Atoms service that delivers Lean4 formal proof capability to an assistant per API call.

What you can do
  • Provides Lean4 formal proof as an atom service on Conduit Atoms, invoked per API call.
  • No tool list, instructions or README are published, so the specific operations an assistant can perform are not documented here.
  • Access is gated by a single gateway key that must carry this atom's scope.
When to use it
Consider it when you want an assistant to reach a hosted Lean4 formal proof service without running proof tooling locally, and you already use or are willing to sign up for the Conduit Atoms gateway.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A Conduit Atoms gateway key is required, sent in the Authorization header as a bearer token, and the key must hold this atom's scope. Sign-up happens on the provider's site.
Before you install
The server requires a secret gateway key in the Authorization header; keep it private and scope-limited. The input gives no detail on what the proof service does with submitted content, so treat anything sent as leaving your machine. Usage may be metered per API call under the provider's terms.

Installation

In SourceWeft

  1. Open Lean4 formal proof — Atom in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.aimlds%2Fatom-lean4-formal-proof/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lean4-formal-proof-atom": {
      "type": "http",
      "url": "https://atoms.pipavia.com/mcp/lean4-formal-proof",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestNov 15, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Proof integrations