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

Sourcery

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

安装

概览

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

Sourcery security findings: MCP server, CLI, and fix-prompt builder over the Sourcery API.

PopNx MCP 的三大支柱

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

它能帮你做什么

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

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

安装

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

安装之前

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

你需要

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

你用的是哪个应用?

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

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

{
  "mcpServers": {
    "sourcery": {
      "command": "npx",
      "args": [
        "-y",
        "@abyssbugg/sourcery"
      ],
      "env": {
        "SOURCERY_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add sourcery --env SOURCERY_API_KEY=your-value -- npx -y @abyssbugg/sourcery

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

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "sourcery": {
      "command": "npx",
      "args": [
        "-y",
        "@abyssbugg/sourcery"
      ],
      "env": {
        "SOURCERY_API_KEY": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "sourcery": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@abyssbugg/sourcery"
      ],
      "env": {
        "SOURCERY_API_KEY": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

  • SOURCERY_API_KEY 机密 必填 env
    Sourcery Team-plan API key with security scanning enabled

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

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • … 尚未检查

    仍在维护

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

  • … 尚未检查

    有许可证

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

  • – 不适用

    端点有响应

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

  • – 不适用

    使用 OAuth 登录

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

  • … 尚未检查

    工具描述中没有隐藏指令

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

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

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

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

常见问题

Sourcery 安全吗?

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

它需要哪些密钥或代码?

你需要填写:SOURCERY_API_KEY

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

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

它还在维护吗?

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

哪些应用可以使用它?

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

有什么可以替代它?

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

替代选择

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

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

FactLot

作者:9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

电脑或云端今天更新
安装

作者的 README

打开 README

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

Sourcery Agent Bundle

A hybrid plugin bundle for agent-driven Sourcery security workflows: an MCP server (12 tools over Sourcery's public security API, pinned OpenAPI snapshot), two Agent Skills, and adapters for Claude Code, Cursor, Codex/ChatGPT, VS Code, Devin, Grok (CLI + Bot), Amp, Hermes, OpenClaw, and Rovo Dev CLI. The server ships as the npm package @abyssbugg/sourcery — most hosts just register npx -y @abyssbugg/sourcery@latest. See docs/COMPATIBILITY.md for per-host install steps.

What is confirmed

Sourcery's current docs say the only public API is a Team-plan REST API for security findings. The documented API base is https://api.sourcery.ai/api, and the first documented request is:

curl https://api.sourcery.ai/api/v1/security-issues \

-H "Authorization: Bearer $SOURCERY_API_KEY"

Verified and pinned. The live OpenAPI document (https://api.sourcery.ai/api/openapi.json) is committed as a snapshot at openapi/sourcery-openapi.json:

  • Info: Sourcery API 0.1.0 (OpenAPI 3.1.0)
  • Fetched: 2026-09-10
  • SHA-256: 9fdb45e657a6406c86ea0d0def2963d534e20bec1a9c88f7d62dbc2e6807f877

Every tool and the client allow-list are wired from that snapshot. The verified surface is exactly eight operations:

MethodPathPurpose
GET/v1/security-issuesList issues (filters + cursor pagination)
GET/v1/security-issues/statsCounts by status and severity
GET/v1/security-issues/{id}Fetch one issue
PATCH/v1/security-issuesBulk update (max 100 ids)
GET/v1/security-issue-groupsList groups (same filters)
GET/v1/security-issue-groups/statsCounts by status and severity
GET/v1/security-issue-groups/{id}Fetch one group including its issues
PATCH/v1/security-issue-groupsBulk update groups (max 100 ids)

Why the Sourcery API + Git connector split

Sourcery's PR review controls are currently documented as GitHub/GitLab comment or label commands (review, summary, guide, title, resolve, dismiss, create issue) rather than public REST endpoints. Those actions are therefore best implemented through your GitHub/GitLab connector, while Sourcery is used for security findings.

Bundle shape

Repo root = plugin root. The portable core (plugin.json + skills/ + mcp.json) follows the Agent Plugins 1.0.0 standard, which Cursor and OpenAI (Codex, ChatGPT desktop) load natively; the other files are thin per-host adapters.

sourcery-agent-bundle/

plugin.json # Agent Plugins core manifest mcp.json # portable stdio wiring -> bin/sourcery skills/ sourcery-triage/SKILL.md # findings triage workflow sourcery-remediate/SKILL.md # minimal-change fix workflow bin/ sourcery # launcher: dist/cli.js when built, else npx @abyssbugg/sourcery agents/ sourcery-triager.md # read-only triage sub-agent (Claude format) .claude-plugin/plugin.json # Claude Code manifest + userConfig API key .mcp.json # Claude Code MCP wiring (npx) .agents/plugins/marketplace.json # Codex/ChatGPT local marketplace entry scripts/ install-rovodev.sh # Rovo Dev CLI wiring (mcp.json + skills) install-local-hosts.sh # grok, amp, hermes, openclaw, VS Code, Devin examples/ mcp.http.json # remote deployment template hooks/ # optional hooks example (SessionStart echo; not enabled) docs/ COMPATIBILITY.md # per-host setup matrix grok-bot-skill.md # paste-in skill for Grok Bot openapi/ sourcery-openapi.json # pinned spec snapshot (SHA-256 above) src/ # TypeScript: MCP server + findings CLI (@abyssbugg/sourcery) constants.ts # pinned facts: operations, enums, spec hash tests/ # TypeScript tests (constants drift pin, tools, client) python/ # Python reference implementation (server, client, prompts) src/sourcery_agent/ tests/ package.json # npm package manifest (@abyssbugg/sourcery) .env.example README.md

Tools

  • sourcery_security_snapshot: counts by status/severity plus the first page of active issues — start here for a triage overview.
  • sourcery_list_findings: list issues with repository_ids, issue_types, statuses, search, limit, cursor.
  • sourcery_get_finding: fetch one issue (full record incl. source snippet and dependency graph).
  • sourcery_get_security_counts: aggregate counts by status and severity.
  • sourcery_bulk_update_findings: bulk status/severity changes (≤100 ids; SOLVED is scanner-owned and rejected).
  • sourcery_list_groups, sourcery_get_group, sourcery_get_group_counts, sourcery_bulk_update_groups: the same capabilities for issue groups.
  • sourcery_build_fix_prompt: builds the Sourcery-style minimal-change agent prompt from a finding; the DEPENDENCY path uses fixed_versions + manifest_file_path and renders the dependency chain.
  • sourcery_capabilities: describes the verified surface, spec pin, and enum values.
  • sourcery_api_request: compatibility bridge restricted to the eight verified operations.

CLI

npx -y @abyssbugg/sourcery@latest snapshot                          # counts + first page of active findings

npx -y @abyssbugg/sourcery@latest list --status ACTIVE --limit 50 # filterable list npx -y @abyssbugg/sourcery@latest get 1234 # one finding in full npx -y @abyssbugg/sourcery@latest fix-prompt 1234 # minimal-change agent prompt

Inside an enabled plugin host, bin/sourcery runs the same CLI (it prefers a locally built dist/cli.js and otherwise falls back to npx). Add --json to any query command for scripting.

Setup

Requirements: Node 20+. Most hosts register the MCP server directly:

export SOURCERY_API_KEY='...'

npx -y @abyssbugg/sourcery@latest # stdio MCP server (no args) npx -y @abyssbugg/sourcery@latest http # Streamable HTTP (127.0.0.1:8765/mcp)

Or install it as a plugin bundle — one step per host (details in docs/COMPATIBILITY.md):

HostQuick start
Claude Codeclaude --plugin-dir . — prompts for the API key on enable
Cursorsymlink the repo into ~/.cursor/plugins/local/, reload
Codex CLI / ChatGPT desktopcodex plugin marketplace add ./
ChatGPT webrun npx -y @abyssbugg/sourcery@latest http behind HTTPS, add via developer mode
VS Code / Grok / Amp / Hermes / OpenClawscripts/install-local-hosts.sh (idempotent; registers plugin, MCP, and skills)
Devinskill links via the installer; devin plugins install --local . for the full plugin
Grok Botpaste-in skill from docs/grok-bot-skill.md
Rovo Dev CLIscripts/install-rovodev.sh

For development and tests, see the Python reference implementation (its suite doubles as the bundle-packaging checker) and run npm test for the TypeScript suite. The server is built on the official MCP TypeScript SDK (@modelcontextprotocol/sdk).

Regenerating the pinned snapshot

When Sourcery publishes a spec change:

curl -sS --fail -o openapi/sourcery-openapi.json https://api.sourcery.ai/api/openapi.json

shasum -a 256 openapi/sourcery-openapi.json # update SPEC_SHA256 in src/constants.ts (+ python/src/sourcery_agent/constants.py, README/docs) npm test # tests/constants.spec.ts fails on drift

Sourcery's PR review commands (review, summary, guide, title, resolve, dismiss, create issue) remain GitHub/GitLab comment or label commands — implement those through your Git provider connector, not the Sourcery REST API.

问 PopNx