# AtpMcp (oci · ghcr.io/jcschuster/atp_mcp) Theorem provers for agents: SystemOnTPTP, StarExec, Isabelle and local ATPs, with SZS verdicts. - Trust score: 45/100 (low) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - oci · `ghcr.io/jcschuster/atp_mcp`: 45/100 (this document), [markdown](https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp.md), [page](https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp) ## Channel facts - Registry: `oci` - Package: `ghcr.io/jcschuster/atp_mcp` - Version: `0.8.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - 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. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 6 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 77/100 - AI-judged instruction clarity (good). - Tool/resource definitions use about 965 tokens (~107/item across 9 items; 9 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **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. ## Install ### 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. ### Claude ```bash claude mcp add jcschuster-atp-mcp -- docker run --rm -i ghcr.io/jcschuster/atp_mcp:0.8.1 ``` ### Cursor ```json { "mcpServers": { "jcschuster-atp-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/jcschuster/atp_mcp:0.8.1" ] } } } ``` ### VS Code ```json { "servers": { "jcschuster-atp-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/jcschuster/atp_mcp:0.8.1" ] } } } ``` ### Codex ```bash codex mcp add jcschuster-atp-mcp -- docker run --rm -i ghcr.io/jcschuster/atp_mcp:0.8.1 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "jcschuster-atp-mcp": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/jcschuster/atp_mcp:0.8.1" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: jcschuster-atp-mcp: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/jcschuster/atp_mcp:0.8.1"] ``` ### Netclaw ```json { "McpServers": { "jcschuster-atp-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/jcschuster/atp_mcp:0.8.1" ] } } } ``` ### Other ```json { "mcpServers": { "jcschuster-atp-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/jcschuster/atp_mcp:0.8.1" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 45, +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. ### 2026-11-03 (score 44, +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. ### 2026-11-01 (score 43, +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. ### 2026-10-31 (score 42, +1) - [functional improvement] Security disclosure: fail → pass ### 2026-10-29 (score 41) First indexed and scored. ## MCP tools (9) ### `list_backends` (~41 tokens) List the AtpClient backends this MCP server exposes (sotptp, isabelle, local_exec, starexec) and their human-readable labels. ### `describe_szs` (~113 tokens) 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. ### `verify_backend` (~51 tokens) 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. Input parameters: - `backend` (string, required): Backend to probe ### `query_backend` (~174 tokens) 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. Input parameters: - `backend` (string, required): Which backend to run on - `problem` (string, required): 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) ### `list_provers` (~22 tokens) List every theorem prover system available on SystemOnTPTP. ### `run_prover` (~163 tokens) 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. Input parameters: - `problem` (string, required): TPTP problem text - `raw` (boolean): Return the system's verbatim output instead of the SZS verdict - `system_id` (string, required): 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 ### `compare_provers` (~112 tokens) 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. Input parameters: - `problem` (string, required): TPTP problem text - `system_ids` (array, required): Prover IDs or bare system names to compare - `time_limit_sec` (integer): Time limit per prover in seconds ### `prove_isabelle` (~201 tokens) 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. Input parameters: - `raw` (boolean): Return the system's verbatim output instead of the SZS verdict - `theory` (string, required): Isabelle theory text - `theory_name` (string, required): Theory name (also used as the .thy filename) - `timeout_ms` (integer): Overall use_theories timeout in milliseconds ### `lint_problem` (~88 tokens) 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. Input parameters: - `backends` (array): Which lint backends to run (default: both) - `problem` (string, required): TPTP problem text ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp#diagnostics ## Score history - 2026-11-05: 45 - 2026-11-04: 44 - 2026-11-03: 44 - 2026-11-02: 43 - 2026-11-01: 43 - 2026-10-31: 42 - 2026-10-30: 41 - 2026-10-29: 41 ## Common questions ### 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. ### What did VerifyMCP test on the AtpMcp MCP server? VerifyMCP ran 12 checks on AtpMcp, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about AtpMcp: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - GitHub Container Registry: https://ghcr.io/jcschuster/atp_mcp - Repository: https://github.com/jcschuster/AtpMcp - Changelog RSS feed: https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp/changelog.json - Trust report (JSON): https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp.json - HTML version of this page: https://verifymcp.io/servers/jcschuster-atp-mcp/ghcr-io-jcschuster-atp-mcp