原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Swarm

作者:SkaleAgents版本 0.12.1i★ 0i电脑或云端官方网站 ↗
注册名称io.github.SkaleAgents/swarm

安装方法

What it does

IaC, CI and dependency security review for coding agents: local scan CLI plus hosted OAuth MCP.

  • Connects 电脑或云端
  • Account or key Cloud: Sign in to the service when you connect (OAuth) · Local: No key needed
  • Category 开发者工具

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

作者:morluto★ 468,7331 个 skill

Skill · 操作手册

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

作者:multica-ai★ 234,3321 个 skill

Skill · 操作手册未注明许可证

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

作者:Graphify-Labs★ 150,2871 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度15/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分35/100

质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Swarm。按照 https://mcp.popnx.com/i/skaleagents-swarm.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/5 项检查 · 你的提问会经过开发者的服务器(skaleagents.com) · ✓ 命令已检查 2026年11月19日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Swarm
    Remote MCP server URL · 地址https://skaleagents.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsSwarm

  4. 试一试

    用 Swarm 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Swarm,或回答中出现 Swarm 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Swarm
    Connection · 地址https://skaleagents.com/mcp
  3. 在聊天中选择 Swarm

    开启新聊天,输入前先从插件列表中选择 Swarm

  4. 试一试

    用 Swarm 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Swarm,或回答中出现 Swarm 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user swarm https://skaleagents.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Swarm 在列表中并显示已连接

  4. 试一试

    用 Swarm 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Swarm,或回答中出现 Swarm 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Swarm 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Swarm,或回答中出现 Swarm 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Swarm 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Swarm,或回答中出现 Swarm 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://skaleagents.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Swarm 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user swarm https://skaleagents.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "swarm": {
      "url": "https://skaleagents.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "swarm": {
      "type": "http",
      "url": "https://skaleagents.com/mcp"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user swarm -- npx -y @skaleagents/swarm

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "swarm": {
      "command": "npx",
      "args": [
        "-y",
        "@skaleagents/swarm"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "swarm": {
      "command": "npx",
      "args": [
        "-y",
        "@skaleagents/swarm"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "swarm": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@skaleagents/swarm"
      ]
    }
  }
}

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

一览

每周下载量i
463/周
许可证i
未注明许可证
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
0.12.1
发布到注册中心i
2026年11月19日
代码最后更新i
2026年11月19日
最近检查
2026年11月19日
作者
SkaleAgents
软件包
npm: @skaleagents/swarm
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✕ 未通过

    有许可证

    仓库中没有找到许可证文件

  • ✓ 通过

    端点有响应

    在 155 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

已公开的漏洞(OSV.dev)

OSV.dev 中没有 @skaleagents/swarm@0.12.1 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月19日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skaleagents-swarm.svg)](https://mcp.popnx.com/en/servers/skaleagents-swarm)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“开发者工具”中的其他服务器比较i

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

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

常见问题

Swarm 安全吗?

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

它需要哪些密钥或代码?

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

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

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(0.12.1)于今天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

作者:ahmedkhaleel2004广泛使用★ 1.9万2个月前更新

在云端运行✓ 服务方 · gitdiagram.comPopNx 团队已实际试用

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

作者:Appllama广泛使用★ 52303个月前更新

在云端运行✓ 服务方 · appllama.io

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

作者:omnara-ai广泛使用★ 34172个月前更新

在云端运行✓ 服务方 · omnara.com

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

作者:repowise-dev广泛使用↓ 6506/周★ 8180 整个仓库的星标6天前更新

电脑或云端✓ 服务方 · repowise.dev
与相似项目对比
本项
Swarm
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查4/54/44/44/44/45/5
许可证–MITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

@skaleagents/swarm

SkaleAgents MCP server. The hosted connection is https://skaleagents.com/mcp.

Quick start

Copy https://skaleagents.com/mcp into your client and choose OAuth. Sign in with Google and click Allow. Leave client ID and secret blank when the client asks. Setup steps for Cursor, Claude Code, Claude Desktop, ChatGPT, and Codex are on the MCP config page.

Tools: plan_architecture_review, review_application_architecture, review_architecture, scan_iac, and scan_dependencies. The older scan_iac_stub name remains an alias for the IaC scanner.

scan_dependencies takes the text of one lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock, composer.lock, requirements.txt or go.sum, up to 2 MB and 5000 packages) and returns known CVEs from OSV.dev as CVE001. It sends ecosystem, package name and version to api.osv.dev, never the lockfile. A failed lookup is an error, not a clean result. For larger lockfiles use scan --cves locally.

review_architecture accepts application source or infrastructure text. Your AI client reads the files in its workspace and sends the relevant content through the MCP tool for a structured review.

Scan locally, in agent hooks, and in pull requests

npx -y @skaleagents/swarm scan [paths...] scans IaC, CI, Dockerfile and package files on your machine. It needs no account and sends nothing over the network unless you pass --cves. Use --changed for files changed against HEAD, --fail-on high to exit 1, and --json for machine output. With --fail-on, a file that cannot be read (invalid syntax, over the size or nesting limit) or a path that does not exist exits 2 instead of passing, the same way a failed CVE lookup does.

Adopt it on an existing repo: npx @skaleagents/swarm scan --write-baseline .skaleagents-baseline.json, commit the file, and later scans show only new findings. The Action reads the baseline from the PR's base commit, so a PR cannot hide findings by editing it. Findings match on rule, file and resource, not line number.

Your own rules. Commit a .skaleagents-rules.json at the repo root and every scan, agent hook and Action run checks it. The agent gets your conventions before it stops, not after review. It applies automatically and needs no account:

{ "rules": [

{ "kind": "require_tag", "resourceType": "aws_s3_bucket", "attribute": "owner", "severity": "medium" }, { "kind": "require_attribute", "resourceType": "aws_db_instance", "attribute": "deletion_protection", "severity": "high" }, { "kind": "forbid_value", "resourceType": "aws_s3_bucket", "attribute": "acl", "value": "public-read", "severity": "high" } ] }

Rules check Terraform .tf files. attribute is a dotted path such as versioning.enabled; a value computed from a variable or expression is skipped with a warning, not flagged. At most 25 rules. A malformed file exits 2 instead of silently skipping the check. Each rule has its own id, like HOUSE483920, shown in the finding; suppress or baseline one rule with # skaleagents-ignore HOUSE483920 reason without hiding the others. A forbid_value value may use letters, digits and . : / + = @ * - _ only. Because computed values are skipped, resolve variables and locals to literals where a rule matters.

scan also looks for committed secrets in any file it reads (AWS, GitHub, Slack, Stripe, Google, npm and Anthropic keys, private keys) as SECRET001, critical. The value is never printed. Git-ignored files such as a local .env are skipped. Rotate the key; only suppress a documented example.

scan --cves also checks the exact package versions in lockfiles against OSV.dev (GitHub Advisories, PyPI, Go, Packagist) and reports known CVEs as CVE001. It reads package-lock.json, pnpm-lock.yaml, yarn.lock, composer.lock, requirements*.txt (exact == pins only) and go.sum. It sends package names and versions to api.osv.dev, never source, and skips npm packages that do not come from the public registry, requirements files that set a custom index, and Go modules matching GOPRIVATE, GONOPROXY or GONOSUMDB (read from the environment, not from go env files). Set PIP_INDEX_URL or PIP_EXTRA_INDEX_URL to skip all requirements files. These filters are best effort. Private names in pnpm and yarn custom registries, and in Composer private repositories, are not detected and would be sent; do not use --cves on those repos. If the lookup fails, the scan exits 2 rather than reporting a clean result. Severity comes from the advisory rating, and unrated advisories show as medium. Accept a known CVE with the baseline file. In the Action, set cves: true; it then checks every tracked lockfile, not only changed ones. The Action only runs on pull requests, so also run a schedule to catch CVEs published after merge:

on: { schedule: [{ cron: "0 6 * * *" }] }

jobs: cves: runs-on: ubuntu-latest steps:

  • uses: actions/checkout@v4
  • run: npx -y --registry=https://registry.npmjs.org @skaleagents/swarm@0.12.1 scan --cves --fail-on high

Suppress an intended setting with a comment on the flagged line or the line above: # skaleagents-ignore DATA001 public asset bucket.

Claude Code plugin. It adds a stop hook that scans changed files, including your .skaleagents-rules.json, and asks the agent to fix high and critical findings, plus a skill and the hosted MCP server:

/plugin marketplace add SkaleAgents/mcp-server

/plugin install skaleagents@skaleagents

Cursor. Add .cursor/hooks.json:

{ "version": 1, "hooks": { "stop": [{ "command": "npx -y --registry=https://registry.npmjs.org @skaleagents/swarm@0.12.1 scan --hook" }] } }

GitHub Action. It posts one PR comment and fails on critical by default:

on: pull_request

permissions: { contents: read, pull-requests: write } jobs: scan: runs-on: ubuntu-latest steps:

  • uses: actions/checkout@v4 with: { fetch-depth: 0 }
  • uses: SkaleAgents/mcp-server@v0.12.1 with: { fail-on: high }

Whole-application consultation

Ask your connected assistant:

Use SkaleAgents as an independent consultant to review this application's

architecture. Read the relevant files, ask me about the important design

decisions, and explain what is sound, what needs changes, and what needs

more evidence.

The architecture_consultation MCP prompt provides this workflow for clients that support prompts. The tools work directly in chat too:

  1. plan_architecture_review takes a repository-relative filePaths inventory and optional context. It suggests files to read and asks up to three questions at a time.
  2. The assistant reads related files through its own workspace tools and calls review_application_architecture with files: [{ path, content }] and the context collected so far.
  3. Answer the follow-up questions. The assistant resubmits the relevant files and updated context, then uses the evidence to review the design and compare alternatives.

The review covers product fit, routing/rendering, module boundaries, data access, authorization, reliability, testing/delivery, and deployment/cost. JavaScript/TypeScript source is parsed into an import graph. Next.js checks include transitive client imports, private environment access, async Client Components, metadata exports, error boundaries, Server Action modules, and explicit Edge runtime incompatibilities. Type-only imports and Server Action boundaries are respected.

Context fields are purpose, criticalFlows, accessControl, data, rendering, deployment, reliability, testing, and constraints. Each holds the owner's answer as text. Calls are stateless: carry answers forward instead of relying on a server-side conversation ID.

Submit up to 80 files, at most 150,000 characters per file and 500,000 combined. Use paths relative to one application package root, including package.json and tsconfig.json or jsconfig.json. Missing imports become evidence requests, not invented findings. The intake accepts up to 3,000 file paths.

Results include an architecture map, referenced findings, an assessment agenda for every review area, and the next questions. The MCP provides static evidence and the connected assistant's model reasons through the architecture. No separate hosted model is invoked, and the tools do not clone repositories or run submitted code. A clean static check is not a whole-system correctness verdict. The MCP config page has an interactive review-brief builder.

Infrastructure scanning

scan_iac parses Terraform HCL/JSON, CloudFormation YAML/JSON, and Kubernetes manifests, including multi-document YAML and Kubernetes Lists. It also reads Dockerfiles, GitHub Actions workflows, Helm templates, Ansible playbooks, Bicep files, and ARM templates. It returns a resource inventory and findings with stable rule IDs, severity, property paths, line locations, and remediation. Findings never include matched secret values.

Checks cover public ingress, wildcard IAM, public storage, encryption settings, bucket versioning, RDS protection, EC2 metadata, Kubernetes privileges, images, resource requests, probes, replicas, inline Secrets, and RBAC. Literal credential and HTTP URL checks also run against parsed resource properties.

Example tool arguments:

{

"content": "resource \"aws_db_instance\" \"app\" { publicly_accessible = true }", "format": "terraform", "focus": "security", "minSeverity": "medium", "maxFindings": 100 }

Both tools accept focus (general, security, reliability, or cost), minSeverity (info through critical), and maxFindings (1 to 500, default 100). Content must contain 1 to 500,000 characters and cannot be whitespace. format defaults to auto; only review_architecture accepts application.

Results are returned as JSON text and MCP structuredContent. totalFindings and totals cover all findings matching the filters; truncated signals that maxFindings limited the returned list. rulesEvaluated lists the IaC checks that ran. Malformed input returns a tool error, not a clean scan.

IaC reviews use the same scanner through either tool. Application reviews use text patterns. Neither mode inspects live infrastructure. Terraform expressions, CloudFormation intrinsics, and external modules are not evaluated. HCL line locations point to resource declarations; property paths identify the setting. YAML aliases must be expanded before submission. Coverage limits are included in every result. An empty finding list is not proof that a system is secure.

Hosted transport

Each hosted tools/call is counted against the account's monthly scan allowance through the API's POST /api/mcp/usage, before the tool runs. Only the API's mcp_scan_limit_reached answer blocks a call, as a tool error with the upgrade text. An outage or timeout (3 seconds) lets the call run. Initialize and tools/list are not counted. The CLI and the stdio package run offline and are not metered.

The web app hosts https://skaleagents.com/mcp using handleMcpRequest from @skaleagents/swarm/http. Audit workers import scanIac from @skaleagents/swarm/scan. It validates each bearer credential with the API's /api/oauth/mcp-token endpoint before running a tool. A successful check is reused for up to 60 seconds, so a revoked token can run tools for up to a minute. Tokens are bound to the MCP resource and cannot access unrelated API routes. Credentials are not forwarded to the public bot directory.

protectedResourceMetadata exports the discovery response for /.well-known/oauth-protected-resource/mcp.

Local development

People working on this repo need Node.js 20 or newer. This is not the way to connect a client.

git clone https://github.com/Skal

只显示了开头部分;其余内容请在仓库中阅读