CHASE MCP server
This repository contains a Model Context Protocol (MCP) server and an agent skill for CHASE (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. With
discharge, the result keeps the terms of the contracts and drops the assumptions discharged by the other contracts. - 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.
- imply and coimply: implication and coimplication, the adjoints of conjunction and disjunction.
- invert: the reciprocal (G, A), the contract seen from its environment.
- assume and ensure: add an assumption or a guarantee.
- remove_vacuous: removes the terms whose removal keeps realizability
and the controllers (where
remove_redundantkeeps A -> G). - is_well_separated: whether the component can win by forcing the environment to violate its assumptions, with that strategy and the assumptions that cause it.
- unrealizable_core and unsat_core: a minimal set of terms that
explains an unrealizable contract, or terms that cannot hold together.
is_realizable,is_compatible,is_consistent, andis_satisfiablereturn it withcore. - 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
.ltlfiles oflogics_tool).
A contract is given in 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 for the checks (free for academic and non-commercial use),
in the
PATHor given with the environment variableCHASE_NUXMV; NuSMV where nuXmv cannot be used. - 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 contains all of them.
Installation
The server is a Python program that runs on the standard input and output.
With 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:
[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):
{"mcpServers": {"chase": {"command": "uvx", "args": ["chase-mcp"]}}}
VS Code uses servers in .vscode/mcp.json:
{"servers": {"chase": {"type": "stdio", "command": "uvx", "args": ["chase-mcp"]}}}
OpenCode uses mcp in opencode.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
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.
Metadata
Release files for chase-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| chase_mcp-0.2.0.tar.gz | 25.0 kB | With provenance | Details for chase_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chase_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for chase_mcp-0.2.0-py3-none-any.whl |
Total release size: 36.0 kB
Release files / chase_mcp-0.2.0.tar.gz
| Download URL | chase_mcp-0.2.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ded7087ff12232a9cfdfe8c683eeaad2fea9b65556aa6d13a660c8e3b98f0b2c
|
|
BLAKE2b-256 checksum How to use checksums |
2ececdc8a7181fab0774cefa012fb7e94579c51ee48bf8179f019afeb835ece9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / chase_mcp-0.2.0-py3-none-any.whl
| Download URL | chase_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2569961e47b0c875404ad0d3bc6c93189308645c28e59a361622813966e3b5b
|
|
BLAKE2b-256 checksum How to use checksums |
6709fe8d4468e6485b7f75a71dbc318d0ab37fda139c65167bb6f422a3f49a9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for chase-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for chase_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.