com.getfootgunPublished by getfootgun.comOfficial publisherv1.0.1Updated Nov 5, 2026
Dated, verified API breakages for coding agents, plus a local scan for them in your existing code.
Footgun gives coding agents a dated, verified registry of third-party API traps, so they can check known breakages before writing code or after an error.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.getfootgun%2Ffootgun/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"footgun": {
"type": "http",
"url": "https://getfootgun.com/api/mcp"
}
}
}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.
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.
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.
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.
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.
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.
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.
Trap data in data/ is licensed CC BY 4.0. Credit "Footgun, getfootgun.com". The plugin files are MIT licensed (see LICENSE).
Source: README.md at commit 4d72f26
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.
contextsurfaceproviderrequiredinclude_staleSearch 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_textrequiredinclude_staleFile 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.
fixrequiredtagsapplyrequiredcauserequiredtitlerequiredsourcesaffectedrequiredproviderrequiredsymptomsrequiredvisibilitysurface_namerequiredsurface_typerequiredConfirm 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_idrequiredhours_loststill_truerequiredversion_seen100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
/plugin marketplace add getfootgun/footgun/plugin install footgun@footgunclaude mcp add --transport http footgun https://getfootgun.com/api/mcp