# DVERA CT verification tools (mcpb · dvera-mcp.mcpb)

DVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage.

- Trust score: 53/100 (low)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `dvera-mcp.mcpb`: 53/100 (this document), [markdown](https://verifymcp.io/servers/suresofttechnologies-dvera-mcp/https-github-com-suresofttechnologies-dvera-plugin-releases-download-v0-1-4-dver.md), [page](https://verifymcp.io/servers/suresofttechnologies-dvera-mcp/https-github-com-suresofttechnologies-dvera-plugin-releases-download-v0-1-4-dver)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/SuresoftTechnologies/dvera-plugin/releases/download/v0.1.4/dvera-mcp.mcpb`
- 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: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/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 43 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 123 tokens (~123/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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).
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 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 DVERA CT verification tools MCP server?

DVERA CT verification tools ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

- Download bundle: `https://github.com/SuresoftTechnologies/dvera-plugin/releases/download/v0.1.4/dvera-mcp.mcpb`

## 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-04 (score 53, −1)

- [functional] Stability: pass → 0.90

### 2026-10-29 (score 54, 0)

- [security] Stability: 0.97 → pass

### 2026-10-28 (score 54, 0)

- [functional] Stability: pass → 0.97

### 2026-10-22 (score 54, 0)

- [security] Stability: 0.97 → pass

### 2026-10-21 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `dvera_check_environment` (~58 tokens)

Check DVERA environment

Report whether a local CT installation is usable by DVERA, and what is missing when it is not. Takes no arguments and needs no CT install, so it is the tool to run when the verification tools are absent from the list.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/suresofttechnologies-dvera-mcp/https-github-com-suresofttechnologies-dvera-plugin-releases-download-v0-1-4-dver#diagnostics

## Score history

- 2026-11-05: 53
- 2026-11-04: 53
- 2026-11-03: 54
- 2026-11-02: 54
- 2026-11-01: 54
- 2026-10-31: 54
- 2026-10-30: 54
- 2026-10-29: 54
- 2026-10-28: 54
- 2026-10-27: 54
- 2026-10-26: 54
- 2026-10-25: 54
- 2026-10-24: 54
- 2026-10-23: 54
- 2026-10-22: 54
- 2026-10-21: 54
- 2026-10-20: 53
- 2026-10-19: 53
- 2026-10-18: 53
- 2026-10-17: 52
- 2026-10-16: 52
- 2026-10-15: 51
- 2026-10-14: 51
- 2026-10-13: 50
- 2026-10-12: 50
- 2026-10-10: 49
- 2026-10-04: 46
- 2026-10-03: 46
- 2026-10-02: 45
- 2026-10-01: 45

## Common questions

### What is the DVERA CT verification tools MCP server?

DVERA CT verification tools is an MCP server listed in the public MCP registry as io.github.SuresoftTechnologies/dvera-mcp. DVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage. This page covers its MCPB bundle (https://github.com/SuresoftTechnologies/dvera-plugin/releases/download/v0.1.4/dvera-mcp.mcpb).

### Is the DVERA CT verification tools MCP server safe to use?

DVERA CT verification tools scores 53 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 DVERA CT verification tools MCP server expose?

DVERA CT verification tools exposes 1 tool: dvera_check_environment. Their descriptions and schemas cost roughly 58 tokens of context every time the server is loaded.

### What licence is the DVERA CT verification tools MCP server under?

DVERA CT verification tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/SuresoftTechnologies/dvera-plugin
- Changelog RSS feed: https://verifymcp.io/servers/suresofttechnologies-dvera-mcp/https-github-com-suresofttechnologies-dvera-plugin-releases-download-v0-1-4-dver.xml
- Changelog JSON feed: https://verifymcp.io/servers/suresofttechnologies-dvera-mcp/https-github-com-suresofttechnologies-dvera-plugin-releases-download-v0-1-4-dver.json
- HTML version of this page: https://verifymcp.io/servers/suresofttechnologies-dvera-mcp/https-github-com-suresofttechnologies-dvera-plugin-releases-download-v0-1-4-dver