DVERA CT verification tools MCP server

DVERA — CT Verification Skills for C/C++ Coding Agents

한국어: README.ko.md

DVERA (Dynamic Verification Agent) brings CT C/C++ verification work into coding agents such as Claude Code, Codex CLI, Cursor, and GitHub Copilot. It uses the working context of source code, requirements, build information, source changes, and existing test assets to prepare and request CT verification work.

CT (Controller Tester) is a test automation solution for unit, integration, and code-based testing of mission-critical C/C++ software. It brings together test-environment setup, test design and generation, execution, code-coverage analysis, reporting, and traceability management.

DVERA does not replace CT's verification results. The coding agent helps prepare and coordinate verification work; CT performs the analysis, build, test execution, and result aggregation. Generated tests must be reviewed for test intent, data, and expected results, then confirmed with actual execution results and measured coverage.

What the CT and DVERA workflow adds

Workflow at a glance

1. Prepare the compiler, macro, include-path, toolchain, and target context for a CT project.
2. Analyze the project and resolve environment or configuration issues through a controlled feedback loop.
3. Generate, execute, and improve unit or integration tests using build, execution, and coverage feedback.
4. Review coverage and results, produce reports, and re-run affected verification after source changes.

The Skills in this repository document that product-connected workflow. They are not standalone replacements for a CT installation.

Install

In Claude Code:

/plugin marketplace add SuresoftTechnologies/dvera-plugin
/plugin install dvera@suresofttech

Or from a terminal:

claude plugin marketplace add SuresoftTechnologies/dvera-plugin
claude plugin install dvera@suresofttech

Skills then load as /dvera:ct-init-project, /dvera:ct-test-loop, and so on. The plugin adds about 620 tokens to every session; each Skill body is read only when that Skill runs.

Product-backed actions need a deployed CT environment. Without one, a Skill stops at its installation check and shows how to reach product support.

Example requests

Trigger examples from the CT user guide. Responses can vary with the AI model and conversation context; if the result differs from what you expect, rephrase the request with more detail and retry.

Skills

All Skills require a deployed CT environment for their product-backed actions and stop with an installation notice when none is found.

Shortened. The full README is on GitHub.