Pwned Coffee

MCP开发工具

提供方 未标注

开发工具 HTTP · 远程 API Key 社区 / 第三方 ClaudeCursorVS CodeWindsurf
查看接入方式

Live security incidents, updated hourly: fix status, fixed versions, lockfile and repo checks. Browse Pwned Coffee MCP Server for Claude, Cursor, VS Code,...

一句话选型结论

按资料字段整理

Pwned Coffee 属于开发工具类 MCP 服务器,HTTP · 远程,API Key,可直接接入 Claude、Cursor、VS Code 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式HTTP · 远程 鉴权API Key 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Development

安装与配置

HTTP · 远程 API Key
连远程 HTTPS 端点,通常为 Streamable HTTP
npx add-mcp 'https://pwned.coffee/mcp'

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Pwned Coffee当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

5.2 KB
来自项目仓库与上游目录的原文,未做删改

pwned.coffee

Live security incidents, updated hourly. pwned.coffee shows what is affected, whether a fix exists, which versions fix it, and the sources behind each answer. It is built from CISA KEV, GitHub security advisories and security news, with every fix status tied to a source you can open. No account, no API key.

This repository is pwned.coffee's home on GitHub: what it is, how to use it, and where to report a wrong entry. The site's source code is not open source. The only public pwned.coffee repositories are this docs repo and pwned-coffee/check-action, the GitHub Action (MIT).

MCP server

A remote, read-only MCP server at https://pwned.coffee/mcp (Streamable HTTP, no authentication, rate limited per IP).

Tool What it does
todays_specials Live incidents right now, optionally filtered by stack ids.
lookup_cve The incident covering a CVE or GHSA id, or a named bug such as HTTP2Shell.
check_lockfile Matches a lockfile's content (optional ecosystem) against incidents that state fixed versions.
check_repo Takes the files that describe what a project runs (lockfiles, Dockerfiles, workflows and more) and says what needs fixing.
whats_new Incidents created or updated since a point in time (24h, 7d or a timestamp), optional stack.
diff_since Every correction, new ticket and fix-status change since a point in time, each with its source.

Prompts: protect_my_repo and morning_check.

Claude Code```sh
claude mcp add --transport http pwned-coffee https://pwned.coffee/mcp


**Cursor** (`.cursor/mcp.json`), and other agents that take the same JSON (Windsurf, Gemini CLI, Zed and more):```json
{
  "mcpServers": {
    "pwned-coffee": { "url": "https://pwned.coffee/mcp" }
  }
}

Codex```sh
codex mcp add pwned-coffee --url https://pwned.coffee/mcp


Then ask your agent to run `check_repo` on your project, or use the `protect_my_repo` prompt.

`registry/server.json` is its entry for the Official MCP Registry (`coffee.pwned/pwned-coffee`).

## Check a lockfile from a terminal or CI```sh
curl -sS -F f=@package-lock.json https://pwned.coffee/api/check

You get a text receipt by default. Send Accept: application/json for JSON. Add ?fail=1 to get a 422 when something is affected.

In GitHub Actions:yaml - uses: pwned-coffee/check-action@v1 # pin it to a commit SHA

The Action sends the repo's lockfiles, Dockerfiles, .nvmrc and workflows to /api/check and fails the job when packages need fixing. See check-action for its inputs.

Feeds and API

Endpoint Returns
https://pwned.coffee/incidents.json Live incidents. ?status=past for older ones, ?stack= to filter, ?since=24h (or an ISO timestamp) for only what changed.
https://pwned.coffee/changes.json Every correction, new ticket and fix-status change since ?since= (default 7 days, at most 90), each with its source. Pass next_since back as since next time.
https://pwned.coffee/feed.xml RSS of the live board, hottest first, same filters.
https://pwned.coffee/i/ One incident page.
https://pwned.coffee/cve/ Redirects a CVE or GHSA id to the incident that covers it (404 when no ticket covers it).
https://pwned.coffee/menu/ Live incidents, history and status for one product. Also as /menu/.json and /menu//llms.txt.
https://pwned.coffee/today.json Today's board as one small JSON (CORS open).
https://pwned.coffee/grade/ A grade from A to F. Badge: /badge/.svg (?grade=1 for the grade).
https://pwned.coffee/breaches, /supply-chain Topic pages.
https://pwned.coffee/health, /data-health.json Data health and the board's rules.
https://pwned.coffee/corrections Every automatic correction, with its source.
https://pwned.coffee/llms.txt A plain-text guide for LLMs and agents, with every field and stack id.

Every JSON feed and feed.xml sends a weak ETag and answers 304 to a matching If-None-Match.

Add ?stack=nextjs,php (any stack ids from llms.txt) to filter.

Report a wrong entry

Found a wrong fix status, fixed version, product, CVE or stack tag, or an incident that's missing?

  • Open a wrong-entry report with the ticket URL or CVE id, what's wrong, and a source link.
  • Or email chef@pwned.coffee.

A fix status on pwned.coffee only comes from a source we store and link, so a link to the vendor advisory, CVE record, GitHub advisory or release notes is what lets us correct it. Corrections show up in the public correction log.

Issues are public. A security problem with pwned.coffee itself goes to security@pwned.coffee (security.txt), not to an issue.

Privacy

Lockfiles and other files you paste or upload to /protect, /api/check, the MCP tools or the GitHub Action are read in memory to answer that one request. They aren't stored and their contents aren't written to logs. Details: pwned.coffee/about#privacy.

Not security advice

pwned.coffee is a summary of public sources. Confirm against the vendor advisory linked on each incident page.

License

The text in this repository is licensed under CC BY 4.0. This covers the docs only, not the pwned.coffee site, its code or its data.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Pwned Coffee 怎么安装?

在客户端按下面的安装命令接入:npx add-mcp 'https://pwned.coffee/mcp'。装完在客户端配置里引用同一个包或端点。

Pwned Coffee 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Pwned Coffee 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Pwned Coffee 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Pwned Coffee 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Windsurf、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Pwned Coffee 能提供哪些能力?

资料显示能力标签包括 Development。具体工具清单以官方文档为准。

Pwned Coffee 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Pwned Coffee 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。