Footgun

com.getfootgun由 getfootgun.com 发布官方发布者v1.0.1更新于 Nov 5, 2026

Dated, verified API breakages for coding agents, plus a local scan for them in your existing code.

已验证Streamable HTTP可网页运行知识与记忆开发者工具

概览

AI 生成的概览

Footgun 为编码助手提供带日期、经核实的第三方 API 陷阱登记库,让它在写代码前或报错后查证已知的破坏性变更。

可以做什么
  • 在针对第三方 API、平台或 AI 工具写代码前,查询经核实、带日期的失效模式与修复方法
  • 粘贴调用失败的错误文本,检索最接近的已核实陷阱
  • 在问题修复后提交新陷阱,公开前会对照官方来源核查
  • 记录某个陷阱是否仍然成立,可选填写损失工时和所见版本
适用场景
适合助手要针对经常变动的第三方 API、平台或 AI 工具写代码时,或调用这类服务失败、希望直接得到已知原因和修复方法而非猜测时。对于模型已熟悉的旧 API 帮助不大。
运行要求
远程 streamable HTTP 端点,无需本地包或运行时。查询和提交无需账号;私密提交和确认陷阱需要 Bearer API 密钥,通过 Authorization 请求头发送,并在服务商账户页创建。
安装前请注意
Authorization 请求头携带密钥,请勿写入共享配置。提交和确认陷阱会把数据发送给服务商,公开提交会对照官方来源审核。配套插件和扫描器独立于此端点,各有自己的遥测设置。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Footgun,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.getfootgun%2Ffootgun/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "footgun": {
      "type": "http",
      "url": "https://getfootgun.com/api/mcp"
    }
  }
}

README

Footgun

Your AI agent knows how the API works. Footgun tells it how it breaks.

Footgun is a dated, verified registry of the traps that docs leave out: silent deprecations, quiet limits, settings that save but do nothing. Your coding agent checks it before it writes the code. Browse every trap at getfootgun.com.

Does it help?

On 17 coding tasks that touch recent API changes, run 5 times each, Claude Code got the code right on the first try 82% of the time with Footgun and 52% without, at 18% lower cost per working result. On older APIs the model already knows, it made no difference. The method and full results are at getfootgun.com/benchmark.

What we found in 200 AI-built apps

89 of 200 still use GitHub Actions built for Node 20, which GitHub now runs on Node 24. 93 have at least one problem that breaks now or will break, counting only rules a person checked against real code. The method and results are at getfootgun.com/scan.

Install in Claude Code

/plugin marketplace add getfootgun/footgun/plugin install footgun@footgun

Lookups and filing work without an account. Filed traps are checked against official sources before anyone else sees them. To confirm traps, create an API key at getfootgun.com/account and enter it when the plugin asks.

The plugin also adds /footgun:scan, which checks your project on your machine for known traps in the exact package versions you use. Your code never leaves your machine; only the rule download and an anonymous count of findings are sent. Turn the plugin setting share_learnings off to stop the count and the filing of fixes your agent learns. The setting auto_context adds a short note of those traps at the start of each session. It is on by default; set it to false to turn it off.

Command line

cli/ holds the same scanner as a command, published on npm as @getfootgun/footgun: npx @getfootgun/footgun scan [path] (Node 20 or later). Add --json for machine-readable output or --fail-on breaks to fail a CI job.

Launch checks come first, under "Before you launch": problems that leak data or run up a bill, such as secret keys in browser code or a Supabase table with RLS off. Ones that live in a dashboard rather than in code are listed as items to check yourself whenever you use that package.

After a scan it prints a dated README badge: "no known API traps" only when the scan found nothing apart from launch reminders, "scanned" otherwise.

With a Pro or Team key, scan --watch adds the project to Footgun Watch, which lists new and changed traps that match your exact package versions on your Projects page. It sends the project name, the folder of each package file, your package names and versions, and the trap, file and line of each finding, never code. See getfootgun.com/docs.

In GitHub Actions, use GetFootgun/scan-action. It lists findings in the job summary, can fail the job on breaks or will-break, and with watch: "true" sends the project to Footgun Watch.

Any other MCP client

claude mcp add --transport http footgun https://getfootgun.com/api/mcp

For Cursor, Codex and other clients, point them at https://getfootgun.com/api/mcp (streamable HTTP). Add the header Authorization: Bearer <your key> to file and confirm traps.

The data

data/traps/<tool>/<trap>.json holds every public verified trap: symptoms, cause, fix, the date it was last verified, and its trust score. data/providers.json lists the tools covered. The data is exported from getfootgun.com and updated as traps are added, confirmed or retired.

Licence

Trap data in data/ is licensed CC BY 4.0. Credit "Footgun, getfootgun.com". The plugin files are MIT licensed (see LICENSE).

来源:README.md,提交 4d72f26

工具

4

lookup_traps

Look up traps for a provider

Call before writing code against a third-party API, platform, or AI tool. Returns verified, dated failure modes with fixes.

输入参数contextsurfaceprovider必填include_stale

search_traps

Search traps by error text

Call when a call to a third-party service fails. Paste the error text. Returns the closest verified traps with fixes.

输入参数providererror_text必填include_stale

file_trap

File a new trap

Draft a trap after a failure was fixed. Private by default with a Pro or Team key. Public filings are checked automatically against official sources and published only when an official source confirms them. A reviewer can still act on any filing. Citing the provider's official documentation or changelog in sources helps. No API key needed. Set visibility to public to submit to the public registry.

输入参数fix必填tagsapply必填cause必填title必填sourcesaffected必填provider必填symptoms必填visibilitysurface_name必填surface_type必填

confirm_trap

Confirm or dispute a trap

Record that a trap is still true (or not), with optional hours lost and version seen. Needs an API key.

输入参数trap_id必填hours_loststill_true必填version_seen

版本历史

2
  1. v1.0.1最新Oct 21, 2026
  2. v1.0.0Oct 19, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分