v0.1.4

No functional change from 0.1.3. The server, its tools and its behaviour are identical.

This release exists so that directories which build from the repository rather than from the release asset pick up the built-in tool added in 0.1.3. One of them published a 0.1.3 build made from an earlier commit, and its published versions cannot be rebuilt or withdrawn, so a new version number was the only way to give it something current to build.

If you are already running 0.1.3, there is nothing here for you.

v0.1.3

Adds a built-in tool, so the server is never an empty one.

dvera_check_environment is answered by the server itself, with no CT installation behind it. It reports whether a local CT install is usable by DVERA and what to do when it is not: no install found, an install too old to ship the MCP bundle, a CT_HOME pointing at a directory that does not exist, an unreadable tool catalog, or an install that appeared after the MCP client started and needs a restart to be picked up.

A machine without CT therefore lists one tool rather than none. Where CT is installed, the 21 verification tools are unchanged and the new one joins them.

Also in this release: the initialize instructions no longer say CT is absent when it is installed but unusable, and a cancellation notification is now applied only to a request that is still outstanding.

v0.1.2

Fixes the version the server reports over the wire.

0.1.1 shipped with SERVER_INFO still set to 0.1.0, so an MCP client saw 0.1.0 in the initialize response while every manifest said 0.1.1. No behaviour change beyond that string.

v0.1.1

Corrects three Skill defects and republishes the bundle so installed copies pick them up.

• ct-test-loop documented the AI test-generation argument as spec; the CT catalog declares specs, an array of requirement strings.
• ct-orchestrator had no row for regression_done and no fallback for an unrecognised status.
• ct-report reported success without checking the tool result first.

The MCP server itself is unchanged. The version bump is what carries the Skill fixes to the plugin directory, which keys updates off the manifest version.

v0.1.0

First release of the DVERA MCP server.

It exposes CT (Controller Tester)'s 21 C/C++ verification tools to an MCP client, so creating a project, running analysis, generating and executing tests, reviewing coverage, and exporting reports all happen in one conversation.

Install

Download dvera-mcp.mcpb and install it in a client that supports MCP bundles. The host provides the Python runtime, so there is nothing to install first.

CT 2026.06 or later must be installed locally for the tools to do anything. Without it the server still starts and reports zero tools, so it is safe to leave configured on any machine. If CT is installed somewhere other than the default location, set its path in the install dialog.

How it is built

• No third-party dependencies. Standard library only.
• No CT product code is bundled or imported. The server reads the tool catalog shipped with the local CT installation and forwards each call to CT's own command-line entry point.
• Every tool carries a title and a consent hint (readOnlyHint / destructiveHint), so a client asks before running anything that changes state.

Verifying the download

sha256  1ef03aec68ce8c8bc6bdc1353150be38c0d1684e426267178c610748acaac046

Note

The Claude Code plugin with 14 Skills is separate from this bundle. See the repository README for how to install it.