prova-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROVA_API_KEY | No | API key from prova.cobound.dev. Demo is rate-limited. | |
| PROVA_LEAN_BIN | No | Path to the Lean 4 executable. | lean |
| PROVA_API_BASE_URL | No | Override for self-hosted Prova. | https://api.prova.cobound.dev |
| PROVA_MCP_LOG_LEVEL | No | Server log level. | WARNING |
| PROVA_DEFAULT_RETAIN | No | Whether verify_reasoning defaults to persisting the original reasoning text. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_reasoningA | Verify a multi-step reasoning chain and return a Prova certificate summary. Use this on any draft chain-of-thought before producing a final answer.
A VALID verdict means the argument is structurally sound (no circularity,
no contradiction, no unsupported leap). An INVALID verdict tells you
exactly which step is broken in the Args: reasoning: The reasoning chain as plain text (numbered steps or prose). retain: If True, the original reasoning text is persisted on the certificate row. Default follows PROVA_DEFAULT_RETAIN env var (False if unset). source_url: Optional URL of a paper or document this reasoning came from — surfaced on the certificate page. domain: Optional hint: medical | legal | financial | code | general. Improves failure-classification accuracy. metadata: Optional caller-defined key/value pairs (<=20 keys, <=8 KB) attached to the certificate. Returns:
Compact certificate summary including verdict, confidence_score,
certificate_id, certificate_url, and (if INVALID) a |
| get_certificateA | Fetch a previously issued certificate by ID (e.g. PRV-2026-A7X4). Returns the same compact summary as |
| download_lean_proofA | Download the self-contained Lean 4 proof for a VALID certificate. INVALID certificates do not have a proof — the call will return an error.
The returned Returns: {certificate_id, lean_source, byte_count} |
| kernel_check_proofA | Run the Lean 4 kernel on a proof string locally. This is the trust-anchor: Prova's verdict is only as strong as its server,
but Requires the Returns: {accepted, exit_code, stdout, stderr, lean_binary, lean_version} |
| verify_and_kernel_checkA | Verify reasoning, then locally kernel-check the emitted Lean proof. The complete trust loop in one call. If the verdict is VALID, the Lean proof is downloaded and handed to the local Lean kernel; the result tells you whether the proof is mathematically sound on your own machine, not Prova's. INVALID verdicts skip the kernel step and return the failure. Returns: {certificate, kernel_check} — kernel_check is null when verdict != VALID or no proof was emitted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear and distinct purpose: downloading proofs, fetching certificates, kernel checking, verifying reasoning, and a combined verify-and-check. There is minimal overlap and descriptions clearly differentiate them.
All tools use consistent snake_case naming with a verb_noun pattern (e.g., download_lean_proof, verify_reasoning). The naming is predictable and follows a clear convention.
With five tools, the server is appropriately scoped for its purpose of reasoning verification and proof checking. Each tool serves a necessary function without being overly numerous or sparse.
The tool set covers the core workflow: verifying reasoning, retrieving certificates, downloading proofs, local kernel checking, and a combined operation. There are no obvious gaps for the intended use case.