原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Gapproof

作者:CloudCorpRecords版本 0.1.0i★ –i在你的电脑上运行
注册名称io.github.CloudCorpRecords/gapproof

安装

概览

作者提供的说明(英文原文)

Find untested functions: link tests to code, score coverage, record proven runs locally.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "gapproof": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/gapproof",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add gapproof -- npx -y @reneturcios/gapproof mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "gapproof": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/gapproof",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "gapproof": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/gapproof",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32464 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32464 个服务器的 88% 更新
  • 基础检查结果等于或优于此分类中其他 32464 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Gapproof 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.0)于4天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, yontu

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

yontu

作者:senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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 .py are classified as tests when they live under test/, 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(, and const name = (...) => (also let/var, the function keyword form, and an optional async). Python: def name(. A Python name not starting with _ counts as exported; a TS/JS name counts as exported when declared with export.
  • Linking. A function is *linked* when its name appears as a word in some test file's content.
  • Proving. orangepro_record_run appends a run (test, outcome: "pass" | "fail", optional functions) 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: /.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

npx @reneturcios/gapproof orangepro_start '{"root":"/path/to/repo"}'

Or run the container image:

docker run -i ghcr.io/cloudcorprecords/gapproof

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.

gapproof orangepro_start '{"root":"/path/to/repo"}'

gapproof orangepro_analyze_sources '{"root":"/path/to/repo"}' gapproof orangepro_find_test_gaps '{"root":"/path/to/repo","limit":10}' gapproof orangepro_status '{"root":"/path/to/repo"}' gapproof orangepro_record_run '{"root":"/path/to/repo","test":"math.test","outcome":"pass"}' gapproof orangepro_export_evidence_pack '{"root":"/path/to/repo"}' gapproof --version

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:

npx -y @reneturcios/gapproof mcp

MCP client configuration:

{

"mcpServers": { "gapproof": { "command": "npx", "args": ["-y", "@reneturcios/gapproof", "mcp"] } } }

Tools

All tools take root (the repository path) unless noted.

ToolExtra inputWhat it returns
orangepro_start—Analyzes the repo, persists .gapproof/graph.json (preserving recorded runs), and returns {root, sources, functions, tests, linked, unlinked} counts.
orangepro_analyze_sources—The same walk without persisting: per-file function lists plus the total function count.
orangepro_find_test_gapslimit (optional)Unlinked functions as [{function, file, exported}], exported first, then in file order.
orangepro_status—With a persisted graph: {exists: true, generated_at, counts}. Without one: {exists: false} plus a fresh, unstored snapshot.
orangepro_doctor—{root_exists, has_manifest, source_files, test_files, issues}; a manifest is package.json or pyproject.toml at the root.
orangepro_graph_score—{score, linked_ratio, proven_ratio, functions} — 60% linked + 40% proven.
orangepro_stats—{files, functions, tests, test_files, linked, unlinked, proven, runs}. tests counts individual test cases; test_files counts files.
orangepro_rtm—[{id, functions, covered}] for requirement ids found in source comments; covered means every associated function is linked. Empty when no ids appear.
orangepro_changed_impactfiles (required array){changed_functions, affected_tests, unlinked_changed} for the given repo-relative changed files.
orangepro_record_runtest, outcome (required), functions (optional)Appends a run to the graph (running a fresh analysis first when no graph exists) and returns {recorded: true, runs_total}.
orangepro_explain_testtest (required)Locates a test file by name substring and returns {test, file, linked_functions, proven_functions, content_excerpt} (excerpt ≤ 400 chars).
orangepro_export_evidence_pack—{generated_at, root, score, stats, gaps, runs}, returned to the caller — nothing is written.

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

npm install

npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, in-memory fixture repo, no network, no disk npm run dev # run the CLI from source via tsx

License

MIT — see LICENSE.

问 PopNx