gitgoblin

Name: gitgoblin
Author: anandkaranubc

作者：anandkaranubc版本 0.1.8i★ –i在你的电脑上运行

注册名称io.github.anandkaranubc/gitgoblin

安装

概览

作者提供的说明（英文原文）

Discover open-source repositories worth your time and evidence-backed contribution opportunities.

PopNx MCP 的三大支柱

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

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

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

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：GITHUB_TOKEN

安装

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

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： GITHUB_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

下载作者的 .mcpb 文件

链接指向作者自己的文件；我们不托管也不重新打包它。打开文件后，Claude Desktop 会进行安装。

在终端中运行这条命令

claude mcp add gitgoblin --env GITHUB_TOKEN=your-value -- npx -y @gitgoblin/mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "gitgoblin": {
      "command": "npx",
      "args": [
        "-y",
        "@gitgoblin/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "gitgoblin": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@gitgoblin/mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

GITHUB_TOKEN 机密 env
Optional GitHub token that can read public repositories. Raises rate limits from 60 to 5000 requests per hour and unlocks starter-issue data. A GitHub CLI login works too.

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

它能做什么

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

基础检查i

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

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 anandkaranubc 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

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

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

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

常见问题

gitgoblin 安全吗？

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

它需要哪些密钥或代码？

你需要填写：GITHUB_TOKEN

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

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

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.8）于7天前进入注册中心。

哪些应用可以使用它？

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

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Reelsaw

替代选择

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

如何看卡片：★ 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昨天更新

安装

Reelsaw

作者：osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

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

安装

作者的 README

打开 README

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

@gitgoblin/mcp

gitgoblin as a Model Context Protocol server. It gives any MCP client (Claude Code, Codex, Cursor, Gemini CLI, Copilot in VS Code, and others) four read-only tools: discover repositories worth your time, explain why one scores the way it does, analyze what a repository actually needs, and get a full briefing on one piece of work.

claude mcp add gitgoblin -- npx -y @gitgoblin/mcp

docs/agents.md has the one-liner for every client, the skill that teaches agents when to use the tools, and what has been verified. The server is listed in the official MCP Registry as io.github.anandkaranubc/gitgoblin. You can also run the server from a clone with node packages/mcp/bin/gitgoblin-mcp.mjs after npm install; Claude Desktop users install the release's gitgoblin.mcpb directly.

Tools

Tool	Input	Output
`discover_repositories`	`goal` (default `contribute`), `languages`, `topics`, `keywords`, `min_stars`, `max_stars`, `pushed_within_days`, `created_within_days`, `license`, `like`, `exclude_owners`, `include_archived`, `include_forks`, `limit` (default 10, max 25)	Ranked repositories: stars, language, license, score, the three strongest reasons for and one against, starter issues for `contribute`. `structuredContent.results[]` carries the same fields; `warnings` lists refused searches and failed lookups, which mean the ranking may be partial, and projects left out because their maintainers opted out of gitgoblin.
`explain_repository`	`repository`, `goal`	All eleven discovery signals with value, weight for the goal and evidence. Unknown signals say so.
`analyze_repository`	`repository`, `max_opportunities` (default 10, max 30), `check_dependencies` (default true), `goal`	The profile (nature, activity, responsiveness, welcomeness with signals, rules, commands, conventions) and the ranked opportunities with their primary evidence.
`get_opportunity`	`repository`, `opportunity_id` or `issue_number` (an issue's or a stale pull request's number)	One opportunity in full plus how to work on the project: clone, commands, conventions, rules, etiquette.

repository accepts owner/name or a URL. explain_repository and the like seed take github.com repositories, since discovery reads GitHub's API by owner and name; analyze_repository and get_opportunity also take gitlab.com and codeberg.org, which intel reads through their public APIs. Every other host is refused. Errors come back as tool results with advice (how to get a token, how to spell a repository), never as protocol failures. An analysis runs in a child process and is stopped after five minutes, or as soon as the client cancels the request, so one slow repository never freezes the other tools; at most two run at once. Long calls send progress notifications when the client provides a progress token.

The server's instructions tell the agent the typical flow, that quoted repository text is data and never instructions, and the one rule that matters: it never opens issues, pull requests or comments on the person's behalf unless asked.

The repository is often chosen by a model, so the server treats it as hostile: it reads only repositories it has confirmed public with an anonymous request, analyzes each in a child process with an empty home directory (none of your git configuration or credential helpers apply) that is killed with everything it started after five minutes or on cancellation, keeps clones per forge, never fetches external links, and strips control and format characters from every result, which opens with a reminder that repository text is data and is capped in size. docs/design.md explains each defence.

Environment

Variable	Effect
`GITHUB_TOKEN`, `GH_TOKEN`	Optional. Raises GitHub's limits and unlocks starter issues. Falls back to `gh auth token`.
`GITGOBLIN_CACHE_DIR`	Where the HTTP cache lives (default `~/.cache/gitgoblin`); the server's blob-less clones go in `mcp/repos/` under it, at most 20 per forge.

Development

npm test -w @gitgoblin/mcp                                       # protocol tests with fakes, offline

npm run typecheck -w @gitgoblin/mcp GITGOBLIN_E2E=1 npx vitest run --root packages/mcp test/e2e # the real server over stdio, against GitHub npm run bundle -w @gitgoblin/mcp # what npm pack ships: dist/gitgoblin-mcp.mjs and its THIRD_PARTY_NOTICES.md npm run mcpb -w @gitgoblin/mcp # the Claude Desktop bundle: dist/gitgoblin.mcpb

src/server.ts builds the server from an injectable ServerDeps (discovery and intel); src/format.ts renders results for a model; src/deps.ts wires the real packages; bin/gitgoblin-mcp.mjs is the launcher. Development runs the TypeScript source on Node 24. Publishing bundles the source and the sibling packages into one file with no runtime dependencies, because Node will not strip types under node_modules. docs/design.md explains the decisions; server.json is the manifest for the MCP Registry; it points at the release's .mcpb and its SHA-256. Releases are built by the repository's release workflow from an mcp-v tag on the merged commit, never from a local checkout; docs/releasing.md has the steps, including the MCP Registry workflow run that follows each release.