Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

COVERA COVER coverage tools

MCPB · COVERA-MCP.MCPB

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

Available components

+5 this week 46 Trust /100

Last scanned (13 hours ago)

Scores higher than 76% of MCPB servers

Category Testing and QA

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • 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.Unverified
  • 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).Unverified
  • Install-script risk not yet assessed.Unverified
  • 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).Unverified
Provenance & Transparency45
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)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 scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)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).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 18 Nov 26 +3
    • Stability: unverified → 0.27 ▲ functional
  • 10 Nov 26 41

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed mcpb/https://github.com/SuresoftTechnologies/covera-plugin/releases/download/mcp-v0.1.0/covera-mcp.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 11 exposed · ~2,223 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
covera_coverage_build ~611

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.

NameTypeReqDescription
artifactsarray–Expected build artifact; repeatable.
decisionstring–Absolute path of an integrity-protected decision file produced by this runner.
executeboolean–Run the validated original and coverage builds after planning. Without it, plan only.
failFastboolean–Stop on the first coverage build failure; do not run the project-file fallback.
gccBuildDirectorystring–GCC build directory.
gccBuildToolstring–Explicit cmake or make executable.
gccCleanTargetstring–Clean target name (default: clean).
gccConfigurationstring–Build configuration.
gccConfigureArgsarray–Extra configure argument; repeatable.
gccCoverConfigstring–COVER config filename under <agent-root>/conf (default: gcc.config).
gccGeneratorstring–CMake generator.
jobContextstring–Absolute path of an existing job.json to resume.
jobsRootstring–Absolute path of the jobs root directory.
noEnvironmentProfileboolean–Do not read a previous job's environment profile.
openApiServerUrlstring–COVER Open API main web server URL (e.g. https://cover.example.com:4009); required for a new build unless already cached.
parallelinteger–Build parallelism (default: host CPU count).
projectDirstring–Absolute path of the project to build (start a new workflow).
serverUrlstring–Local Agent remote-service URL; defaults to CODESCROLL_TM_SERVER_URL.
stm32cubeideExecutablestring–Explicit stm32cubeidec.exe / stm32cubeide for headless builds.
targetsarray–Native GCC build target; repeatable.
verifyTlsboolean–Verify the HTTPS certificate for a new COVER job (skipped by default).
vsRealToolsarray–Fallback cl.exe/link.exe/lib.exe as TOOL=PATH; repeatable.

No output schema declared.

No examples provided.

covera_coverage_measure ~251

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).

NameTypeReqDescription
detailsboolean–Include per-file and per-function coverage, not just the module summary.
limitinteger–Rows per detail page (1-2000, default 100).
maxPagesinteger–Maximum detail pages to read (default 1000).
moduleIdstring–24-hex build module id (not a symbolicmoduleid URL).
moduleNamestring–Full filename or path suffix of the module to find. The server may return several candidates.
serverUrlstring–COVER Open API main web server URL; defaults to the cached one.
verifyTlsboolean–Verify the HTTPS certificate and hostname (skipped by default).

No output schema declared.

No examples provided.

covera_doctor ~77

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

covera_get_guide ~72

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.

NameTypeReqDescription
topicstringyesWhich procedure to read.

No output schema declared.

No examples provided.

covera_recovery_collect ~260

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.

NameTypeReqDescription
agentRootstring–Absolute path of the COVER EE Local Agent install folder, if it should override the environment.
archivestringyesAbsolute path for the new error ZIP (required).
hardwareFilestring–Absolute path of the build account's HardwareID file.
hardwareIdstring–Build Agent HardwareID; omit to read it from the build account file.
projectRootstring–Absolute path of the build working directory where the analysis-error command ran.
runDirstringyesAbsolute path of the new run directory (required).
searchRootsarray–Extra folders or ZIP files to search; repeatable.
serverstring–COVER server root URL for this recovery.
serverRootstring–Absolute path of a local COVER server install folder or catalina.home.
sourcestringyesSource identifier of the analysis error (required).
verifyTlsboolean–Verify the HTTPS certificate and hostname. Omitted, TLS verification is skipped (the default on internal COVER servers with self-signed certificates).

No output schema declared.

No examples provided.

covera_recovery_discover ~230

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.

NameTypeReqDescription
agentRootstring–Absolute path of the COVER EE Local Agent install folder, if it should override the environment.
hardwareFilestring–Absolute path of the build account's HardwareID file.
hardwareIdstring–Build Agent HardwareID; omit to read it from the build account file.
projectRootstring–Absolute path of the build working directory where the analysis-error command ran.
searchRootsarray–Extra folders or ZIP files to search; repeatable.
serverstring–COVER server root URL for this recovery.
serverRootstring–Absolute path of a local COVER server install folder or catalina.home.
sourcestringyesSource identifier of the analysis error (required).
verifyTlsboolean–Verify the HTTPS certificate and hostname. Omitted, TLS verification is skipped (the default on internal COVER servers with self-signed certificates).

No output schema declared.

No examples provided.

covera_recovery_inspect ~41

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

NameTypeReqDescription
casestringyesAbsolute path of the case directory (required).

No output schema declared.

No examples provided.

covera_recovery_publish ~118

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.

NameTypeReqDescription
casestringyesAbsolute path of the case directory (required).
planDigeststringyesplan_digest from publish-plan (required).
serverstringyesCOVER server root URL (required).
verifyTlsboolean–Verify the HTTPS certificate (skipped by default).

No output schema declared.

No examples provided.

covera_recovery_publish_plan ~121

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.

NameTypeReqDescription
casestringyesAbsolute path of the case directory (required).
hardwareIdstringyesBuild Agent HardwareID (required).
serverstringyesCOVER server root URL (required).
verifyTlsboolean–Verify the HTTPS certificate (skipped by default).
wrapperstringyesWrapper name to connect (required).

No output schema declared.

No examples provided.

covera_recovery_start ~289

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.

NameTypeReqDescription
agentRootstring–Absolute path of the COVER EE Local Agent install folder, if it should override the environment.
artifactsstring–Absolute path of error material; omit to auto-find from the build context.
hardwareFilestring–Absolute path of the build account's HardwareID file.
hardwareIdstring–Build Agent HardwareID; omit to read it from the build account file.
projectRootstring–Absolute path of the build working directory where the analysis-error command ran.
runDirstringyesAbsolute path of the new run directory to create (required).
searchRootsarray–Extra folders or ZIP files to search; repeatable.
serverstring–COVER server root URL for this recovery.
serverRootstring–Absolute path of a local COVER server install folder or catalina.home.
sourcestringyesSource identifier of the analysis error (required).
verifyTlsboolean–Verify the HTTPS certificate and hostname. Omitted, TLS verification is skipped (the default on internal COVER servers with self-signed certificates).

No output schema declared.

No examples provided.

covera_recovery_verify ~153

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.

NameTypeReqDescription
candidatestringyesAbsolute path of the candidate file (required).
casestringyesAbsolute path of the case directory (required).
platformstring–Build PC OS; omit to let the server decide.
serverstring–COVER server root URL; defaults to the case's collection server.
timeoutinteger–Status-poll wait in seconds (1-60); the server run continues regardless.
verifyTlsboolean–Verify the HTTPS certificate (skipped by default).

No output schema declared.

No examples provided.

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.

mcpb · covera-mcp.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

841ff6a5bec515b4066cc3537a812fb148bb8b35ea34b7f33f19c57c9e44cadb

macOS / Linux

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

Windows (PowerShell)

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

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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.