
Gapproof
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Find untested functions: link tests to code, score coverage, record proven runs locally.
Overview
Gapproof's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Gapproof in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
gapproof
gapproof is a local test-gap analysis tool for a code repository. It walks the sources, extracts the functions it finds, checks which of them are mentioned by a test, and reports the gaps: functions no test appears to cover. Recorded test runs add a second, stronger signal — a function named by a passing run (directly, or through the test that links it) counts as proven, not just linked — and the two signals combine into a single coverage score.
This package is a clean-room rebuild, and a labelled core subset:
it covers 12 of the 18 tools documented for the original Orangepro
MCP server (orangepro_*). The omitted tools are listed under
"Scope" below.
How it works — honestly
There is no AST, no parser, and no network call anywhere. The engine is a set of documented heuristics:
- Walk. Starting at the given root, it skips
node_modules,.git,dist, and dot-directories. Files ending in.ts,.tsx,.js,.jsx, or.pyare classified as tests when they live undertest/,tests/, or__tests__/, or are named*.test.*,*.spec.*,test_*.py, or*_test.py; all others are sources. - Extraction (regex). TypeScript/JavaScript:
function name(,export function name(, andconst name = (...) =>(alsolet/var, thefunctionkeyword form, and an optionalasync). Python:def name(. A Python name not starting with_counts as exported; a TS/JS name counts as exported when declared withexport. - Linking. A function is linked when its name appears as a word in some test file's content.
- Proving.
orangepro_record_runappends a run (test,outcome: "pass" | "fail", optionalfunctions) to the persisted graph. A function is proven when a passing run names the function, or names a test file / test case that links it. - Score.
60% × linked ratio + 40% × proven ratio, reported on a 0–100 scale with one decimal place. - RTM. Requirement ids matching
[A-Z]+-\d+are read from source comments only (//,/* … */,#) and associated with the functions defined in the same file.
State lives in one file: <root>/.gapproof/graph.json, written by
orangepro_start and orangepro_record_run. Everything else reads
the repository (and that graph, when runs matter) without writing.
Install
Or run the container image:
The container defaults to the MCP server. Pass CLI arguments to use it as a CLI instead. No API key is needed — the original's optional model key only powers its AI test-generation tools, which this subset omits.
CLI
The CLI mirrors the tools: one subcommand per tool, taking its arguments as a single JSON object.
Exit codes: 0 on success, 1 on an analysis or validation error,
2 for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
MCP client configuration:
Tools
All tools take root (the repository path) unless noted.
Scope
Omitted from this core subset: orangepro_prove_loop,
orangepro_prove, orangepro_generate_tests,
orangepro_update_graph, orangepro_ai_links, and
orangepro_ai_flows. Those are the original's proof-execution and
AI-assisted tools; the AI flows need a model key in the original.
This subset reproduces the local analysis surface only, with the
heuristic limits stated above: name-based linking can miss indirect
coverage and can credit a coincidental mention, and comment-based
RTM extraction only sees ids written in comments.
Development
License
MIT — see LICENSE.
Source: README.md at commit 41d9d7f
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts