io.github.CloudCorpRecords/gapproof
OCI · GHCR.IO/CLOUDCORPRECORDS/GAPPROOF · 2 COMPONENTS
Find untested functions: link tests to code, score coverage, record proven runs locally.
Available components
Last scanned (12 hours ago)
Scores higher than 46% of OCI servers
Category Testing and QA
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: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 546 tokens (~45/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.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.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 40
First indexed and scored.
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 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/gapproof@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
orangepro_analyze_sources ~39
Analyze source files and list the functions found in each, without persisting.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_changed_impact ~50
Report functions changed in the given files, affected tests, and unlinked changes.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Array of strings. |
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_doctor ~39
Check a repository layout: root, manifest, sources, tests, and issues.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_explain_test ~55
Explain one test file: its linked and proven functions and a content excerpt.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
| test | string | yes | Name or path of the test file to explain. |
No output schema declared.
No examples provided.
orangepro_export_evidence_pack ~43
Return an evidence pack with score, stats, gaps, and recorded runs; writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_find_test_gaps ~54
List functions with no linked test, exported first, then in file order.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of test gaps to return. |
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_graph_score ~45
Score test coverage: 60% linked ratio plus 40% proven ratio, 0 to 100.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_record_run ~73
Record a test run outcome against the gap graph.
| Name | Type | Req | Description |
|---|---|---|---|
| functions | array | – | Array of strings. |
| outcome | string | yes | Test run outcome: pass or fail. |
| root | string | yes | Path to the repository root directory. |
| test | string | yes | Test file or test case name for the run. |
No output schema declared.
No examples provided.
orangepro_rtm ~35
Extract requirement ids from source comments and report their covering functions.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_start ~36
Analyze a repository, persist its gap graph, and return summary counts.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_stats ~39
Return counts of files, functions, tests, links, proven functions, and runs.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
orangepro_status ~38
Report whether a persisted gap graph exists, with counts, or a fresh snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | Path to the repository root directory. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/gapproof MCP server?
io.github.CloudCorpRecords/gapproof runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/gapproof:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/gapproof
claude mcp add cloudcorprecords-gapproof -- docker run --rm -i ghcr.io/cloudcorprecords/gapproof:0.1.0
What is the io.github.CloudCorpRecords/gapproof MCP server?
io.github.CloudCorpRecords/gapproof is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/gapproof. Find untested functions: link tests to code, score coverage, record proven runs locally. This page covers its container image (ghcr.io/cloudcorprecords/gapproof).
Is the io.github.CloudCorpRecords/gapproof MCP server safe to use?
io.github.CloudCorpRecords/gapproof scores 41 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 io.github.CloudCorpRecords/gapproof MCP server expose?
io.github.CloudCorpRecords/gapproof exposes 12 tools: orangepro_start, orangepro_analyze_sources, orangepro_find_test_gaps, orangepro_status, orangepro_doctor, and 7 more. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/gapproof MCP server still maintained?
io.github.CloudCorpRecords/gapproof is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/gapproof MCP server under?
io.github.CloudCorpRecords/gapproof declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.