chase-mcp 0.1.0__tar.gz

chase_mcp-0.1.0/.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "chase-cps",
+  "description": "Plugins of the CHASE project (https://chase-cps.github.io).",
+  "owner": {
+    "name": "CHASE developers"
+  },
+  "plugins": [
+    {
+      "name": "chase",
+      "source": "./",
+      "description": "MCP server and skill for assume-guarantee contracts with CHASE."
+    }
+  ]
+}

chase_mcp-0.1.0/.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "chase",
+  "version": "0.1.0",
+  "description": "Assume-guarantee contracts in LTL with CHASE: composition, quotient, refinement, consistency, compatibility, and realizability checks, with counterexamples.",
+  "author": {
+    "name": "CHASE developers"
+  },
+  "homepage": "https://chase-cps.github.io",
+  "repository": "https://github.com/chase-cps/chase-mcp",
+  "license": "BSD-3-Clause"
+}

chase_mcp-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  test:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install chase-cps from source
+        run: |
+          sudo apt-get update && sudo apt-get install -y uuid-dev libxml2 libedit2
+          pip install "chase-cps @ git+https://github.com/chase-cps/chase@master"
+
+      - name: Cache the back ends
+        uses: actions/cache@v4
+        with:
+          path: ~/.chase
+          key: chase-tools-nuxmv-2.2.0
+
+      - name: Install nuXmv with chase-cps install
+        run: test -x ~/.chase/bin/nuXmv || chase-cps install nuxmv --accept-license
+
+      - name: Install and test
+        run: |
+          pip install ".[test]"
+          pytest -q

chase_mcp-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,84 @@
+name: Release
+
+# Builds the chase-mcp package.
+# - Manual run: the package is uploaded to TestPyPI, with the version
+#   X.Y.Z.devN (N is the number of the run), so that each run can be uploaded.
+# - Tag v*: the package is uploaded to PyPI.
+# Both use trusted publishing: the PyPI (and TestPyPI) project must list this
+# repository, this workflow (release.yml), and the environment (pypi, testpypi).
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-22.04
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Check that the tag matches the version
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          version=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml', 'rb'))['project']['version'])")
+          test "${GITHUB_REF_NAME#v}" = "$version"
+          grep -q "__version__ = \"$version\"" chase_mcp/__init__.py
+
+      - name: Use a development version on TestPyPI
+        if: github.event_name == 'workflow_dispatch'
+        shell: bash
+        run: |
+          python3 - "pyproject.toml chase_mcp/__init__.py" "${{ github.run_number }}" <<'PY'
+          import re, sys
+          files, run = sys.argv[1].split(), sys.argv[2]
+          for f in files:
+              s = open(f).read()
+              s = re.sub(r'^(version|__version__) = "([^"]+)"', rf'\1 = "\2.dev{run}"', s, flags=re.M)
+              open(f, "w").write(s)
+          PY
+
+      - name: Build
+        run: |
+          pip install build
+          python -m build
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  testpypi:
+    if: github.event_name == 'workflow_dispatch'
+    needs: build
+    runs-on: ubuntu-22.04
+    environment: testpypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          skip-existing: true
+
+  pypi:
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: build
+    runs-on: ubuntu-22.04
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist
+      - uses: pypa/gh-action-pypi-publish@release/v1

chase_mcp-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+__pycache__/
+*.egg-info/
+build/
+dist/
+.venv/
+.pytest_cache/
+.DS_Store

chase_mcp-0.1.0/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "chase": {
+      "command": "uvx",
+      "args": ["chase-mcp"]
+    }
+  }
+}

chase_mcp-0.1.0/LICENSE

@@ -0,0 +1,28 @@
+BSD 3-Clause License
+
+Copyright (c) 2026 by University of California, Berkeley
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

chase_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,197 @@
+Metadata-Version: 2.5
+Name: chase-mcp
+Version: 0.1.0
+Summary: MCP server exposing the contract operations of CHASE as agent-callable tools
+Project-URL: Homepage, https://chase-cps.github.io
+Project-URL: Repository, https://github.com/chase-cps/chase-mcp
+Project-URL: Issues, https://github.com/chase-cps/chase-mcp/issues
+Author-email: Yifeng Xiao <yifengx@berkeley.edu>
+License-Expression: BSD-3-Clause
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: chase-cps>=0.1
+Requires-Dist: mcp<3,>=2
+Requires-Dist: pydantic>=2
+Provides-Extra: test
+Requires-Dist: pytest; extra == 'test'
+Description-Content-Type: text/markdown
+
+# CHASE MCP server
+
+This repository contains a [Model Context Protocol][MCP] (MCP) server and an
+agent skill for [CHASE][WEB] (Contract-based Heterogeneous Analysis and
+Systems Exploration).
+
+The server exposes the contract operations of CHASE as tools that an AI agent
+can call: an agent can write assume-guarantee contracts, compose them, check
+refinement, and use the counterexamples returned by the model checker to fix
+the specification. The skill tells the agent how to use these tools.
+
+## Tools
+
+Contract operations that build contracts (each tool returns a new
+contract):
+
+- **compose**: parallel composition of two or more contracts; variables with
+  the same name are connected.
+- **conjoin** and **disjoin**: conjunction and disjunction (greatest lower
+  bound and least upper bound).
+- **merge**: merging of viewpoints of the same component.
+- **divide**: the quotient, i.e. the contract of a missing component.
+- **separate**: separation, the adjoint of merging.
+- **saturate**: the equivalent contract (A, A -> G).
+- **simplify**: rewrites the formulas, as the simplify command of
+  `logics_tool` (negations moved to the atoms, temporal operators grouped).
+- **remove_redundant**: removes the assumptions and guarantees implied by the
+  other terms of the contract.
+
+Contract operations that check contracts (each tool returns a status and,
+when the check fails, a counterexample):
+
+- **refines**: whether a contract refines another one, and which part fails
+  (assumptions or guarantees).
+- **verify**: compatibility and consistency; **is_compatible** (some
+  environment satisfies the assumptions) and **is_consistent** (some behavior
+  satisfies the contract) check them one at a time.
+- **is_realizable**: GR(1) realizability, with the counter-strategy of the
+  environment when unrealizable; **synthesize** also builds the controller.
+- **accepts** and **implements**: whether the contract accepts an
+  environment, and whether an implementation implements the contract, both
+  given as LTL formulas.
+
+LTL formulas:
+
+- **implies** and **is_satisfiable**: validity of an implication and
+  satisfiability of a formula.
+
+Specifications:
+
+- **read_spec** and **write_spec**: read and write contracts in the logics
+  language of CHASE (the `.ltl` files of `logics_tool`).
+
+A contract is given in JSON:
+
+```json
+{"name": "Arbiter",
+ "inputs": {"req": "bool", "n": [0, 3]},
+ "outputs": {"grant": "bool"},
+ "assumptions": ["G F !req"],
+ "guarantees": ["G (req -> F grant)"]}
+```
+
+Variables are Boolean (`"bool"`) or bounded integers (`[low, high]`). Formulas
+use the standard LTL syntax: `! & | -> <-> G F X U R W`, relations, arithmetic,
+and `x'` for the value of `x` in the next step.
+
+## Requirements
+
+- The CHASE Python package, `chase-cps`, installed with the server.
+- [nuXmv][NUXMV] for the checks (free for academic and non-commercial use),
+  in the `PATH` or given with the environment variable `CHASE_NUXMV`;
+  [NuSMV][NUSMV] where nuXmv cannot be used.
+- [slugs][SLUGS] for the realizability checks.
+
+`chase-cps install nuxmv --accept-license` and `chase-cps install slugs`
+install them, and `chase-cps doctor` shows the tools found.
+The [CHASE Docker image][CHASE] contains all of them.
+
+## Installation
+
+The server is a Python program that runs on the standard input and output.
+With [uv][UV] there is nothing to install: `uvx chase-mcp` downloads and runs
+it. Otherwise:
+
+`$> pip install chase-mcp`
+
+and use `chase-mcp` in place of `uvx chase-mcp` below.
+
+Until the first release on PyPI, install from the repositories:
+
+`$> pip install "chase-cps @ git+https://github.com/chase-cps/chase" "chase-mcp @ git+https://github.com/chase-cps/chase-mcp"`
+
+### Claude Code
+
+The server and the skill are packaged as a plugin:
+
+```
+/plugin marketplace add chase-cps/chase-mcp
+/plugin install chase@chase-cps
+```
+
+Or only the server:
+
+`$> claude mcp add chase -- uvx chase-mcp`
+
+### Codex
+
+`$> codex mcp add chase -- uvx chase-mcp`
+
+or, in `~/.codex/config.toml`:
+
+```toml
+[mcp_servers.chase]
+command = "uvx"
+args = ["chase-mcp"]
+```
+
+### Cursor, Claude Desktop, Gemini CLI, and other clients
+
+Most MCP clients read the same JSON configuration. Add the server to the
+`mcpServers` object of the configuration file (`.cursor/mcp.json` or
+`~/.cursor/mcp.json` for Cursor, `claude_desktop_config.json` for Claude
+Desktop, `~/.gemini/settings.json` for Gemini CLI):
+
+```json
+{"mcpServers": {"chase": {"command": "uvx", "args": ["chase-mcp"]}}}
+```
+
+VS Code uses `servers` in `.vscode/mcp.json`:
+
+```json
+{"servers": {"chase": {"type": "stdio", "command": "uvx", "args": ["chase-mcp"]}}}
+```
+
+OpenCode uses `mcp` in `opencode.json`:
+
+```json
+{"mcp": {"chase": {"type": "local", "command": ["uvx", "chase-mcp"]}}}
+```
+
+To set the model checker, add `"env": {"CHASE_NUXMV": "/path/to/nuXmv"}` to
+the server entry (`environment` in OpenCode, `env = { ... }` in Codex).
+
+## Skill
+
+The skill is in `skills/chase-contracts`. It follows the [Agent Skills][SKILLS]
+format (a `SKILL.md` file with instructions), and it also works without the
+MCP server: the agent then uses the `chase_cps` Python package. The
+`examples` folder of the skill contains complete examples; each one is run by
+the tests, so the results they state are the ones CHASE returns.
+
+- Claude Code: installed with the plugin, or copy the folder to
+  `~/.claude/skills/`.
+- Codex: copy the folder to `~/.agents/skills/` (or `.agents/skills/` in a
+  project).
+- Other agents that support Agent Skills: copy the folder to their skills
+  directory.
+
+## Testing
+
+`$> pip install ".[test]"`
+
+`$> pytest`
+
+The tests need nuXmv (`chase-cps install nuxmv --accept-license`).
+
+## License
+
+This project is released under the 3-Clause BSD License.
+
+[MCP]: https://modelcontextprotocol.io
+[WEB]: https://chase-cps.github.io
+[CHASE]: https://github.com/chase-cps/chase
+[NUXMV]: https://nuxmv.fbk.eu/
+[NUSMV]: https://nusmv.fbk.eu/
+[SLUGS]: https://github.com/VerifiableRobotics/slugs
+[UV]: https://docs.astral.sh/uv/
+[SKILLS]: https://agentskills.io

chase_mcp-0.1.0/README.md

@@ -0,0 +1,179 @@
+# CHASE MCP server
+
+This repository contains a [Model Context Protocol][MCP] (MCP) server and an
+agent skill for [CHASE][WEB] (Contract-based Heterogeneous Analysis and
+Systems Exploration).
+
+The server exposes the contract operations of CHASE as tools that an AI agent
+can call: an agent can write assume-guarantee contracts, compose them, check
+refinement, and use the counterexamples returned by the model checker to fix
+the specification. The skill tells the agent how to use these tools.
+
+## Tools
+
+Contract operations that build contracts (each tool returns a new
+contract):
+
+- **compose**: parallel composition of two or more contracts; variables with
+  the same name are connected.
+- **conjoin** and **disjoin**: conjunction and disjunction (greatest lower
+  bound and least upper bound).
+- **merge**: merging of viewpoints of the same component.
+- **divide**: the quotient, i.e. the contract of a missing component.
+- **separate**: separation, the adjoint of merging.
+- **saturate**: the equivalent contract (A, A -> G).
+- **simplify**: rewrites the formulas, as the simplify command of
+  `logics_tool` (negations moved to the atoms, temporal operators grouped).
+- **remove_redundant**: removes the assumptions and guarantees implied by the
+  other terms of the contract.
+
+Contract operations that check contracts (each tool returns a status and,
+when the check fails, a counterexample):
+
+- **refines**: whether a contract refines another one, and which part fails
+  (assumptions or guarantees).
+- **verify**: compatibility and consistency; **is_compatible** (some
+  environment satisfies the assumptions) and **is_consistent** (some behavior
+  satisfies the contract) check them one at a time.
+- **is_realizable**: GR(1) realizability, with the counter-strategy of the
+  environment when unrealizable; **synthesize** also builds the controller.
+- **accepts** and **implements**: whether the contract accepts an
+  environment, and whether an implementation implements the contract, both
+  given as LTL formulas.
+
+LTL formulas:
+
+- **implies** and **is_satisfiable**: validity of an implication and
+  satisfiability of a formula.
+
+Specifications:
+
+- **read_spec** and **write_spec**: read and write contracts in the logics
+  language of CHASE (the `.ltl` files of `logics_tool`).
+
+A contract is given in JSON:
+
+```json
+{"name": "Arbiter",
+ "inputs": {"req": "bool", "n": [0, 3]},
+ "outputs": {"grant": "bool"},
+ "assumptions": ["G F !req"],
+ "guarantees": ["G (req -> F grant)"]}
+```
+
+Variables are Boolean (`"bool"`) or bounded integers (`[low, high]`). Formulas
+use the standard LTL syntax: `! & | -> <-> G F X U R W`, relations, arithmetic,
+and `x'` for the value of `x` in the next step.
+
+## Requirements
+
+- The CHASE Python package, `chase-cps`, installed with the server.
+- [nuXmv][NUXMV] for the checks (free for academic and non-commercial use),
+  in the `PATH` or given with the environment variable `CHASE_NUXMV`;
+  [NuSMV][NUSMV] where nuXmv cannot be used.
+- [slugs][SLUGS] for the realizability checks.
+
+`chase-cps install nuxmv --accept-license` and `chase-cps install slugs`
+install them, and `chase-cps doctor` shows the tools found.
+The [CHASE Docker image][CHASE] contains all of them.
+
+## Installation
+
+The server is a Python program that runs on the standard input and output.
+With [uv][UV] there is nothing to install: `uvx chase-mcp` downloads and runs
+it. Otherwise:
+
+`$> pip install chase-mcp`
+
+and use `chase-mcp` in place of `uvx chase-mcp` below.
+
+Until the first release on PyPI, install from the repositories:
+
+`$> pip install "chase-cps @ git+https://github.com/chase-cps/chase" "chase-mcp @ git+https://github.com/chase-cps/chase-mcp"`
+
+### Claude Code
+
+The server and the skill are packaged as a plugin:
+
+```
+/plugin marketplace add chase-cps/chase-mcp
+/plugin install chase@chase-cps
+```
+
+Or only the server:
+
+`$> claude mcp add chase -- uvx chase-mcp`
+
+### Codex
+
+`$> codex mcp add chase -- uvx chase-mcp`
+
+or, in `~/.codex/config.toml`:
+
+```toml
+[mcp_servers.chase]
+command = "uvx"
+args = ["chase-mcp"]
+```
+
+### Cursor, Claude Desktop, Gemini CLI, and other clients
+
+Most MCP clients read the same JSON configuration. Add the server to the
+`mcpServers` object of the configuration file (`.cursor/mcp.json` or
+`~/.cursor/mcp.json` for Cursor, `claude_desktop_config.json` for Claude
+Desktop, `~/.gemini/settings.json` for Gemini CLI):
+
+```json
+{"mcpServers": {"chase": {"command": "uvx", "args": ["chase-mcp"]}}}
+```
+
+VS Code uses `servers` in `.vscode/mcp.json`:
+
+```json
+{"servers": {"chase": {"type": "stdio", "command": "uvx", "args": ["chase-mcp"]}}}
+```
+
+OpenCode uses `mcp` in `opencode.json`:
+
+```json
+{"mcp": {"chase": {"type": "local", "command": ["uvx", "chase-mcp"]}}}
+```
+
+To set the model checker, add `"env": {"CHASE_NUXMV": "/path/to/nuXmv"}` to
+the server entry (`environment` in OpenCode, `env = { ... }` in Codex).
+
+## Skill
+
+The skill is in `skills/chase-contracts`. It follows the [Agent Skills][SKILLS]
+format (a `SKILL.md` file with instructions), and it also works without the
+MCP server: the agent then uses the `chase_cps` Python package. The
+`examples` folder of the skill contains complete examples; each one is run by
+the tests, so the results they state are the ones CHASE returns.
+
+- Claude Code: installed with the plugin, or copy the folder to
+  `~/.claude/skills/`.
+- Codex: copy the folder to `~/.agents/skills/` (or `.agents/skills/` in a
+  project).
+- Other agents that support Agent Skills: copy the folder to their skills
+  directory.
+
+## Testing
+
+`$> pip install ".[test]"`
+
+`$> pytest`
+
+The tests need nuXmv (`chase-cps install nuxmv --accept-license`).
+
+## License
+
+This project is released under the 3-Clause BSD License.
+
+[MCP]: https://modelcontextprotocol.io
+[WEB]: https://chase-cps.github.io
+[CHASE]: https://github.com/chase-cps/chase
+[NUXMV]: https://nuxmv.fbk.eu/
+[NUSMV]: https://nusmv.fbk.eu/
+[SLUGS]: https://github.com/VerifiableRobotics/slugs
+[UV]: https://docs.astral.sh/uv/
+[SKILLS]: https://agentskills.io

chase_mcp-0.1.0/chase_mcp/__init__.py

@@ -0,0 +1,3 @@
+"""MCP server for CHASE: contract operations as agent-callable tools."""
+
+__version__ = "0.1.0"

chase_mcp-0.1.0/chase_mcp/__main__.py

@@ -0,0 +1,3 @@
+from .server import main
+
+main()