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

Fetter MCP

作者:fetter-io版本 2.0.0i★ 1i在云端运行官方网站 ↗
注册名称io.github.fetter-io/fetter-mcp

安装方法

What it does

Real-time package and vulnerability data (Python, npm, Cargo, Go, and more) for AI coding agents.

  • Connects 在云端运行
  • Account or key No key needed
  • Category 开发者工具

可搭配使用

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

rea

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

作者:morluto★ 467,2351 个 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,1251 个 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★ 149,8731 个 skill

Skill · 操作手册

为什么排在这里

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

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

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

安装

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

通过 2/4 项检查 · 在你的电脑上运行

我们隐藏了部分命令

通过地址连接:检查时服务器地址没有响应

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器 · 作者的安装说明 · 同类的其他服务器

第一步:你用哪个 AI?

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

Claude 暂时无法连接 Fetter MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

ChatGPT 暂时无法连接 Fetter MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

你可以改用这些方式

B · 开发者工具 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Fetter MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

Cursor 暂时无法连接 Fetter MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

VS Code 暂时无法连接 Fetter MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

卡住了?问问正在用 Fetter MCP 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
2.0.0
发布到注册中心i
2026年11月18日
代码最后更新i
2026年11月18日
最近检查
2026年11月16日
作者
fetter-io
网站
fetter.io
注册状态
活跃

哪些应用可以使用它

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

通过互联网连接,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

我们上次检查时服务器没有响应,所以无法读取它的工具。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

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

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✕ 未通过

    有许可证

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

  • ✕ 未通过

    端点有响应

    我们检查时,6 秒内没有响应

  • – 不适用

    使用 OAuth 登录

    我们检查时,6 秒内没有响应

  • … 尚未检查

    工具描述中没有隐藏指令

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

我们检查什么 → · JSON

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

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

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

讨论

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

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

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

登录后发帖

用户评价

还没有评价

登录后写评价

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

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

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

常见问题

Fetter MCP 安全吗?

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

它需要哪些密钥或代码?

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

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

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

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

哪些应用可以使用它?

支持 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
与相似项目对比
本项
Fetter MCP
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查2/44/44/44/44/45/5
许可证–MITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

Fetter MCP

Fetter provides a remote Model Context Protocol (MCP) server at https://mcp.fetter.io/mcp that gives AI coding agents real-time access to package vulnerability data. Built on fetter, it queries package registries and OSV to surface known CVEs, CVSS scores, and safe versions so your agent can make informed dependency decisions as it writes code.

Supported ecosystems: Python (PyPI), npm, Cargo (crates.io), GitHub Actions, VS Code extensions (Open VSX), Go, Ruby (RubyGems), PHP (Packagist), and Swift. Python is the default.

Tools:

  • most_recent_not_vulnerable: find the latest release of a package that is free of known vulnerabilities
  • is_vulnerable: check whether a specific pinned version has known CVEs
  • lookup: find available versions and their vulnerabilities for any package or requirement
  • list_ecosystems: list the supported ecosystems, with each one's name format and examples

Installation

The Fetter MCP server uses the HTTP transport and requires no local installation. Just register the remote URL with your MCP client.

Claude Code
claude mcp add --transport http fetter https://mcp.fetter.io/mcp
Codex
codex mcp add fetter --url https://mcp.fetter.io/mcp
Other MCP Clients

For any other MCP-compatible client, provide the following remote server URL using the HTTP transport:

https://mcp.fetter.io/mcp

Agent Usage

Once installed, the Fetter MCP tools are available to your AI agent during coding sessions. The agent can call them automatically when adding or auditing dependencies; no explicit tool invocation is required in your prompts.

Example prompts

  • "Add the latest safe version of requests to requirements.txt"
  • "Are there any known vulnerabilities in my current dependencies?"
  • "What is the most recent version of lodash with no CVEs?"
  • "Before pinning cryptography, check whether 42.0.5 is vulnerable"
  • "Is actions/download-artifact@v4.1.2 safe to use in this workflow?"

The agent selects the appropriate tool based on context:

  • Adding a new package: most_recent_not_vulnerable to find a safe version
  • Validating a specific pinned version: is_vulnerable for a definitive answer
  • Auditing an existing specifier: lookup to see affected versions

Ecosystems and Package Names

Every lookup tool takes an optional ecosystem parameter. When it is omitted, the ecosystem is python. Ecosystems can be named by their fetter name (python, npm, cargo, gha, vscode, go, ruby, php, swift) or by their OSV name (e.g. PyPI, crates.io, RubyGems), case-insensitively.

Python packages use PEP 508 specifiers (requests==2.31.0, numpy>=2.0). Packages of other ecosystems use name@requirement, with the requirement in that ecosystem's native syntax:

EcosystemExact versionRequirement
pythonrequests==2.31.0requests>=2.30,<3
npmlodash@4.17.15lodash@>=4.17.15 <4.17.22
cargotime@=0.1.43serde@^1.0
ghatj-actions/changed-files@v35actions/download-artifact (all tags)
vscodems-python.python@2024.0.1ms-python.python@>=2024.0.0
gogolang.org/x/net@v0.17.0golang.org/x/net@>=v0.20.0 1.16.0
phpguzzlehttp/guzzle@7.4.0guzzlehttp/guzzle@~7.4.0
swiftgithub.com/sparkle-project/Sparkle@2.8.1github.com/sparkle-project/Sparkle@>=2.6.0 <2.9.0

Every result includes the ecosystem it was looked up in. Each vulnerability carries its ID, summary, maximum CVSS score, severity (Low, Medium, High, Critical), and an OSV URL. Results are returned as structuredContent, with the same JSON also serialized as a text content block for clients that do not read structured content.

list_ecosystems

List the supported ecosystems, the default ecosystem, and, for each, its registry, name format, and example names.

Parameters: none

Example Response (abridged)

{

"default": "python", "ecosystems": [ { "name": "npm", "osv_name": "npm", "registry": "npm registry (registry.npmjs.org)", "name_format": "name@requirement with an npm semver range; scoped names allowed", "exact_example": "lodash@4.17.15", "range_example": "lodash@>=4.17.15 <4.17.22" } ] }

most_recent_not_vulnerable

Find the most recent version of a package that has no known vulnerabilities. Provide only a package name and the server will check the latest release. Useful when pinning a dependency to the latest clean release.

Parameters

  • name: the package name, without a version (e.g. "requests", "lodash", "actions/checkout"). For ecosystems other than Python, an @requirement range may be given to search within.
  • ecosystem: optional; defaults to "python"

Example Request

{

"jsonrpc": "2.0", "method": "tools/call", "id": 2, "params": { "name": "most_recent_not_vulnerable", "arguments": { "name": "lodash", "ecosystem": "npm" } } }

Example Response (`structuredContent`)

{

"ecosystem": "npm", "package": "lodash", "version": "4.18.1", "vulnerabilities": [], "vulnerable": false }

is_vulnerable

Check if a specific package version has known vulnerabilities. Requires an exact version: name==version for Python, name@version for other ecosystems. (For Cargo, a bare version is treated as exact, so time@0.1.43 and time@=0.1.43 are equivalent here.)

Parameters

  • name: the exact package version, e.g. "requests==2.31.0" or "time@=0.1.43"
  • ecosystem: optional; defaults to "python"

Example Request

{

"jsonrpc": "2.0", "method": "tools/call", "id": 2, "params": { "name": "is_vulnerable", "arguments": { "name": "time@=0.1.43", "ecosystem": "cargo" } } }

Example Response (`structuredContent`)

{

"ecosystem": "cargo", "package": "time", "version": "0.1.43", "vulnerabilities": [ { "cvss_score": 6.2, "id": "GHSA-wcg3-cvx6-7396", "severity": "Medium", "summary": "Segmentation fault in time", "url": "https://osv.dev/vulnerability/GHSA-wcg3-cvx6-7396" }, { "cvss_score": 6.2, "id": "RUSTSEC-2020-0071", "severity": "Medium", "summary": "Potential segfault in the time crate", "url": "https://osv.dev/vulnerability/RUSTSEC-2020-0071" } ], "vulnerable": true }

lookup

Look up a package by name and optional version requirement to find which versions are available and whether they have known vulnerabilities. Supports requirements such as "requests", "numpy>=2.0", "lodash@>=4.17.15 <4.17.22", or "actions/download-artifact".

Parameters

  • name: the package name with an optional requirement
  • ecosystem: optional; defaults to "python"
  • limit: when the name is not an exact version, limit the number of recent versions checked
  • cvss_filter: "all" (default) for all vulnerabilities, "max" for only the highest CVSS score per version, or a number (0–10) to keep only vulnerabilities at or above that score
  • retain_passing: include versions with no known vulnerabilities in the results (default: false)

Example Request

{

"jsonrpc": "2.0", "method": "tools/call", "id": 2, "params": { "name": "lookup", "arguments": { "name": "actions/download-artifact@v4.1.2", "ecosystem": "gha" } } }

Example Response (`structuredContent`)

{

"ecosystem": "gha", "package": "actions/download-artifact", "versions": [ { "version": "v4.1.2", "vulnerabilities": [ { "cvss_score": 8.6, "id": "GHSA-cxww-7g56-2vh6", "severity": "High", "summary": "@actions/download-artifact has an Arbitrary File Write via artifact extraction", "url": "https://osv.dev/vulnerability/GHSA-cxww-7g56-2vh6" } ], "vulnerable": true } ] }

If some versions could not be checked against OSV, they are listed in an unaudited array; these are not known to be free of vulnerabilities.

Self-Hosting

The server listens on port 8080 at /mcp. Environment variables:

  • TENANT_SECRET: when set, requests must carry it in the X-Fetter-MCP-Internal header
  • MCP_ALLOWED_HOSTS: comma-separated hostnames accepted in the Host header (DNS-rebinding protection); defaults to loopback and mcp.fetter.io. Use * to disable the check.
  • RUST_LOG: log filter (default info,fetter_mcp=debug)

GitHub Actions and Swift lookups run git ls-remote, so git must be installed.