AtpMcp
OCI · GHCR.IO/JCSCHUSTER/ATP_MCP
Theorem provers for agents: SystemOnTPTP, StarExec, Isabelle and local ATPs, with SZS verdicts.
Available components
Last scanned (9 hours ago)
Scores higher than 64% of OCI servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 965 tokens (~107/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Security disclosure: fail → pass ▲ functional
- 29 Oct 26 41
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/jcschuster/atp_mcp@0.8.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_provers ~112
Submit a TPTP problem to multiple SystemOnTPTP provers simultaneously and report SZS Ontology verdicts side-by-side. Useful for cross-checking or finding the fastest prover for a problem class. Call `describe_szs` for the vocabulary used in the output.
| Name | Type | Req | Description |
|---|---|---|---|
| problem | string | yes | TPTP problem text |
| system_ids | array | yes | Prover IDs or bare system names to compare |
| time_limit_sec | integer | – | Time limit per prover in seconds |
No output schema declared.
No examples provided.
describe_szs ~113
Return a text description of the SZS Ontology (https://tptp.org/UserDocs/SZSOntology/), the vocabulary every other tool uses to report verdicts. Enumerates each Success status (Theorem, Unsatisfiable, Satisfiable, CounterSatisfiable, …) and NoSuccess status (GaveUp, Timeout, ResourceOut, Forced, …) with a short gloss so an agent can decide what a verdict means without leaving the MCP session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lint_problem ~88
Run syntax and type diagnostics on a TPTP problem. By default combines the in-process structural checker with TPTP4X on SystemOnTPTP; pass `backends: ["local"]` for the cheap pass only.
| Name | Type | Req | Description |
|---|---|---|---|
| backends | array | – | Which lint backends to run (default: both) |
| problem | string | yes | TPTP problem text |
No output schema declared.
No examples provided.
list_backends ~41
List the AtpClient backends this MCP server exposes (sotptp, isabelle, local_exec, starexec) and their human-readable labels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_provers ~22
List every theorem prover system available on SystemOnTPTP.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prove_isabelle ~201
Submit a hand-written Isabelle/HOL theory to the Isabelle server configured for this MCP server. The theory text is written into the configured shared directory and processed via `use_theories` on the long-lived session held by `AtpMcp.IsabelleSession` (session name, host, port, and credentials all come from application config — they are fixed for the lifetime of the server and cannot be overridden per call). For TPTP/THF problems use `query_backend` with `backend: "isabelle"` instead — that routes through `prove_tptp` on the same shared session.
| Name | Type | Req | Description |
|---|---|---|---|
| raw | boolean | – | Return the system's verbatim output instead of the SZS verdict |
| theory | string | yes | Isabelle theory text |
| theory_name | string | yes | Theory name (also used as the .thy filename) |
| timeout_ms | integer | – | Overall use_theories timeout in milliseconds |
No output schema declared.
No examples provided.
query_backend ~174
Run a TPTP-format problem through any AtpClient backend and return the normalised SZS Ontology verdict (Theorem, Unsatisfiable, Satisfiable, CounterSatisfiable, GaveUp, Timeout, ResourceOut, …). The unified `AtpClient.Backend.query/2` entry point — each backend hides its ceremony (session, prover selection, theory bookkeeping) behind this call. Call `describe_szs` for the full ontology.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | yes | Which backend to run on |
| problem | string | yes | TPTP problem text |
| raw | boolean | – | Return the system's verbatim output instead of the SZS verdict |
| time_limit_sec | integer | – | Time limit for backends that honour it (sotptp) |
No output schema declared.
No examples provided.
run_prover ~163
Submit a TPTP-format problem to a specific prover on SystemOnTPTP. Returns the SZS Ontology verdict (Theorem, Unsatisfiable, Satisfiable, CounterSatisfiable, GaveUp, Timeout, ResourceOut, …) or raw output. Call `describe_szs` for the full ontology.
| Name | Type | Req | Description |
|---|---|---|---|
| problem | string | yes | TPTP problem text |
| raw | boolean | – | Return the system's verbatim output instead of the SZS verdict |
| system_id | string | yes | Prover ID from list_provers ("Vampire---5.0.1"), or a bare system name ("Vampire") for the latest version offered |
| time_limit_sec | integer | – | Time limit in seconds |
No output schema declared.
No examples provided.
verify_backend ~51
Probe a backend's configuration and reachability. Returns "OK" if the backend is wired up correctly, otherwise an error describing what is missing or unreachable.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | yes | Backend to probe |
No output schema declared.
No examples provided.
How do I install the AtpMcp MCP server?
AtpMcp runs locally as a container image, launched with docker run --rm -i ghcr.io/jcschuster/atp_mcp:0.8.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/jcschuster/atp_mcp
claude mcp add jcschuster-atp-mcp -- docker run --rm -i ghcr.io/jcschuster/atp_mcp:0.8.1
What is the AtpMcp MCP server?
AtpMcp is an MCP server listed in the public MCP registry as io.github.jcschuster/atp_mcp. Theorem provers for agents: SystemOnTPTP, StarExec, Isabelle and local ATPs, with SZS verdicts. This page covers its container image (ghcr.io/jcschuster/atp_mcp).
Is the AtpMcp MCP server safe to use?
AtpMcp scores 45 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AtpMcp MCP server expose?
AtpMcp exposes 9 tools: list_backends, describe_szs, verify_backend, query_backend, list_provers, and 4 more. Their descriptions and schemas cost roughly 965 tokens of context every time the server is loaded.
Is the AtpMcp MCP server still maintained?
AtpMcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AtpMcp MCP server under?
AtpMcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.