# COVERA COVER coverage tools (mcpb · covera-mcp.mcpb)

Drive Suresoft COVER EE from a coding agent: coverage builds, coverage lookup, toolchain recovery.

- Trust score: 46/100 (low)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `covera-mcp.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp.md), [page](https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/SuresoftTechnologies/covera-plugin/releases/download/mcp-v0.1.0/covera-mcp.mcpb`
- Transport: `stdio`
- SHA-256: `841ff6a5bec515b4066cc3537a812fb148bb8b35ea34b7f33f19c57c9e44cadb`

## 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-21.

- **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 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2414 tokens (~219/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); 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 COVERA COVER coverage tools MCP server?

COVERA COVER coverage 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. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 841ff6a5bec515b4066cc3537a812fb148bb8b35ea34b7f33f19c57c9e44cadb; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/SuresoftTechnologies/covera-plugin/releases/download/mcp-v0.1.0/covera-mcp.mcpb`
- SHA-256: `841ff6a5bec515b4066cc3537a812fb148bb8b35ea34b7f33f19c57c9e44cadb`

### Verify on macOS / Linux

```bash
echo "841ff6a5bec515b4066cc3537a812fb148bb8b35ea34b7f33f19c57c9e44cadb  covera-mcp.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\covera-mcp.mcpb).Hash -eq "841ff6a5bec515b4066cc3537a812fb148bb8b35ea34b7f33f19c57c9e44cadb"
```

## 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-21 (score 46, +1)

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

### 2026-11-19 (score 45, +1)

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

### 2026-11-18 (score 44, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-11-10 (score 41)

First indexed and scored.

## MCP tools (11)

### `covera_doctor` (~77 tokens)

Check the COVERA environment

Report whether this MCP server can drive COVER: the Python it runs on, whether CODESCROLL_TM_INSTALL_PATH points at a COVER EE Local Agent, whether cached Open API credentials exist, whether COVER_ACCESS_KEY is set, and which skill entry scripts are present. Needs no project. Run this first when other tools fail with setup errors.

### `covera_get_guide` (~72 tokens)

Read a COVERA skill procedure

Return the procedure a COVERA skill follows, so a client without the skills can work the same way. Topics cover the coverage build flow, module measurement, and toolchain recovery, plus their reference documents. Read the matching topic before driving a flow.

Input parameters:

- `topic` (string, required): Which procedure to read.

### `covera_coverage_measure` (~251 tokens)

Look up module coverage

Read a module's coverage results from the COVER server: the module summary, and optionally per-file and per-function detail. Read-only; runs nothing and changes nothing. Give exactly one of a module name (a filename or path suffix to search for) or a 24-hex module id. The server URL and Access Key come from the Local Agent's cached Open API credentials; set CODESCROLL_TM_INSTALL_PATH if they are not found (see covera_doctor).

Input parameters:

- `details` (boolean): Include per-file and per-function coverage, not just the module summary.
- `limit` (integer): Rows per detail page (1-2000, default 100).
- `maxPages` (integer): Maximum detail pages to read (default 1000).
- `moduleId` (string): 24-hex build module id (not a symbolicmoduleid URL).
- `moduleName` (string): Full filename or path suffix of the module to find. The server may return several candidates.
- `serverUrl` (string): COVER Open API main web server URL; defaults to the cached one.
- `verifyTls` (boolean): Verify the HTTPS certificate and hostname (skipped by default).

### `covera_coverage_build` (~611 tokens)

Run a COVER coverage build

Drive a COVER EE coverage build for a C/C++, C#, or Java project: identify the original build and real tools, plan the instrumented build keeping the original output paths, and -- when execute is true -- run it and keep the successful setup for later builds. Give projectDir to start a new build or jobContext to resume one (exactly one). execute runs the real builds and registers the coverage module on the COVER server, so it changes the project's build setup and server state: read covera_get_guide topic=build first, explain what it does, and get the user's approval before calling with execute. With execute omitted it only plans and writes job state. The result is a workflow envelope; a WAITING_* status means resume with its jobContext after supplying what it asks for. The Open API Access Key is read from the Local Agent's cached credentials or COVER_ACCESS_KEY; this server never prompts for it.

Input parameters:

- `artifacts` (array): Expected build artifact; repeatable.
- `decision` (string): Absolute path of an integrity-protected decision file produced by this runner.
- `execute` (boolean): Run the validated original and coverage builds after planning. Without it, plan only.
- `failFast` (boolean): Stop on the first coverage build failure; do not run the project-file fallback.
- `gccBuildDirectory` (string): GCC build directory.
- `gccBuildTool` (string): Explicit cmake or make executable.
- `gccCleanTarget` (string): Clean target name (default: clean).
- `gccConfiguration` (string): Build configuration.
- `gccConfigureArgs` (array): Extra configure argument; repeatable.
- `gccCoverConfig` (string): COVER config filename under <agent-root>/conf (default: gcc.config).
- `gccGenerator` (string): CMake generator.
- `jobContext` (string): Absolute path of an existing job.json to resume.
- `jobsRoot` (string): Absolute path of the jobs root directory.
- `noEnvironmentProfile` (boolean): Do not read a previous job's environment profile.
- `openApiServerUrl` (string): COVER Open API main web server URL (e.g. https://cover.example.com:4009); required for a new build unless already cached.
- `parallel` (integer): Build parallelism (default: host CPU count).
- `projectDir` (string): Absolute path of the project to build (start a new workflow).
- `serverUrl` (string): Local Agent remote-service URL; defaults to CODESCROLL_TM_SERVER_URL.
- `stm32cubeideExecutable` (string): Explicit stm32cubeidec.exe / stm32cubeide for headless builds.
- `targets` (array): Native GCC build target; repeatable.
- `verifyTls` (boolean): Verify the HTTPS certificate for a new COVER job (skipped by default).
- `vsRealTools` (array): Fallback cl.exe/link.exe/lib.exe as TOOL=PATH; repeatable.

### `covera_recovery_discover` (~230 tokens)

Survey a recovery (read-only)

Read the build environment, COVER server settings, and available analysis-error material without changing anything, and report what is missing to collect it. Read-only.

Input parameters:

- `agentRoot` (string): Absolute path of the COVER EE Local Agent install folder, if it should override the environment.
- `hardwareFile` (string): Absolute path of the build account's HardwareID file.
- `hardwareId` (string): Build Agent HardwareID; omit to read it from the build account file.
- `projectRoot` (string): Absolute path of the build working directory where the analysis-error command ran.
- `searchRoots` (array): Extra folders or ZIP files to search; repeatable.
- `server` (string): COVER server root URL for this recovery.
- `serverRoot` (string): Absolute path of a local COVER server install folder or catalina.home.
- `source` (string, required): Source identifier of the analysis error (required).
- `verifyTls` (boolean): Verify the HTTPS certificate and hostname. Omitted, TLS verification is skipped (the default on internal COVER servers with self-signed certificates).

### `covera_recovery_start` (~289 tokens)

Start a recovery case

Copy the analysis-error ZIP/folder (or collect the latest from the server) into a new run directory and record initial evidence and state. Does not modify original sources. May download from the COVER server, which needs COVER_ACCESS_KEY or cached credentials.

Input parameters:

- `agentRoot` (string): Absolute path of the COVER EE Local Agent install folder, if it should override the environment.
- `artifacts` (string): Absolute path of error material; omit to auto-find from the build context.
- `hardwareFile` (string): Absolute path of the build account's HardwareID file.
- `hardwareId` (string): Build Agent HardwareID; omit to read it from the build account file.
- `projectRoot` (string): Absolute path of the build working directory where the analysis-error command ran.
- `runDir` (string, required): Absolute path of the new run directory to create (required).
- `searchRoots` (array): Extra folders or ZIP files to search; repeatable.
- `server` (string): COVER server root URL for this recovery.
- `serverRoot` (string): Absolute path of a local COVER server install folder or catalina.home.
- `source` (string, required): Source identifier of the analysis error (required).
- `verifyTls` (boolean): Verify the HTTPS certificate and hostname. Omitted, TLS verification is skipped (the default on internal COVER servers with self-signed certificates).

### `covera_recovery_collect` (~260 tokens)

Collect error material from the server

Download the latest PA analysis-error material over the Open API into a new ZIP and start the case. Needs COVER_ACCESS_KEY or cached credentials.

Input parameters:

- `agentRoot` (string): Absolute path of the COVER EE Local Agent install folder, if it should override the environment.
- `archive` (string, required): Absolute path for the new error ZIP (required).
- `hardwareFile` (string): Absolute path of the build account's HardwareID file.
- `hardwareId` (string): Build Agent HardwareID; omit to read it from the build account file.
- `projectRoot` (string): Absolute path of the build working directory where the analysis-error command ran.
- `runDir` (string, required): Absolute path of the new run directory (required).
- `searchRoots` (array): Extra folders or ZIP files to search; repeatable.
- `server` (string): COVER server root URL for this recovery.
- `serverRoot` (string): Absolute path of a local COVER server install folder or catalina.home.
- `source` (string, required): Source identifier of the analysis error (required).
- `verifyTls` (boolean): Verify the HTTPS certificate and hostname. Omitted, TLS verification is skipped (the default on internal COVER servers with self-signed certificates).

### `covera_recovery_verify` (~153 tokens)

Verify a recovery candidate

Run a server-side PA verification of an evidence-backed candidate for a case. Runs analysis on the COVER server but makes no permanent server change. Needs COVER_ACCESS_KEY or cached credentials.

Input parameters:

- `candidate` (string, required): Absolute path of the candidate file (required).
- `case` (string, required): Absolute path of the case directory (required).
- `platform` (string): Build PC OS; omit to let the server decide.
- `server` (string): COVER server root URL; defaults to the case's collection server.
- `timeout` (integer): Status-poll wait in seconds (1-60); the server run continues regardless.
- `verifyTls` (boolean): Verify the HTTPS certificate (skipped by default).

### `covera_recovery_inspect` (~41 tokens)

Inspect a recovery case

Read the recorded run history of a case. Local and read-only.

Input parameters:

- `case` (string, required): Absolute path of the case directory (required).

### `covera_recovery_publish_plan` (~121 tokens)

Plan a server change

Produce a server change plan for a verified case; reads the COVER server only. Returns a plan_digest to pass to covera_recovery_publish. Needs COVER_ACCESS_KEY or cached credentials.

Input parameters:

- `case` (string, required): Absolute path of the case directory (required).
- `hardwareId` (string, required): Build Agent HardwareID (required).
- `server` (string, required): COVER server root URL (required).
- `verifyTls` (boolean): Verify the HTTPS certificate (skipped by default).
- `wrapper` (string, required): Wrapper name to connect (required).

### `covera_recovery_publish` (~118 tokens)

Apply a server change

Apply a verified plan to the COVER server and connect the wrapper. This changes the shared COVER server, so confirm with the user first. Pass the plan_digest from covera_recovery_publish_plan. Needs COVER_ACCESS_KEY or cached credentials.

Input parameters:

- `case` (string, required): Absolute path of the case directory (required).
- `planDigest` (string, required): plan_digest from publish-plan (required).
- `server` (string, required): COVER server root URL (required).
- `verifyTls` (boolean): Verify the HTTPS certificate (skipped by default).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp#diagnostics

## Score history

- 2026-11-21: 46
- 2026-11-20: 45
- 2026-11-19: 45
- 2026-11-18: 44
- 2026-11-17: 41
- 2026-11-16: 41
- 2026-11-15: 41
- 2026-11-14: 41
- 2026-11-13: 41
- 2026-11-12: 41
- 2026-11-11: 41
- 2026-11-10: 41

## Common questions

### What is the COVERA COVER coverage tools MCP server?

COVERA COVER coverage tools is an MCP server listed in the public MCP registry as io.github.SuresoftTechnologies/covera-mcp. Drive Suresoft COVER EE from a coding agent: coverage builds, coverage lookup, toolchain recovery. This page covers its MCPB bundle (https://github.com/SuresoftTechnologies/covera-plugin/releases/download/mcp-v0.1.0/covera-mcp.mcpb).

### Is the COVERA COVER coverage tools MCP server safe to use?

COVERA COVER coverage tools scores 46 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 COVERA COVER coverage tools MCP server expose?

COVERA COVER coverage tools exposes 11 tools: covera_doctor, covera_get_guide, covera_coverage_measure, covera_coverage_build, covera_recovery_discover, and 6 more. Their descriptions and schemas cost roughly 2,223 tokens of context every time the server is loaded.

### What licence is the COVERA COVER coverage tools MCP server under?

COVERA COVER coverage 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.

### What did VerifyMCP test on the COVERA COVER coverage tools MCP server?

VerifyMCP ran 12 checks on COVERA COVER coverage tools, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about COVERA COVER coverage tools: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/SuresoftTechnologies/covera-plugin
- Changelog RSS feed: https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp.json
- HTML version of this page: https://verifymcp.io/servers/suresofttechnologies-covera-mcp/covera-mcp
