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 分