Skip to content
Official MCP RegistryListed

Footgun

Part ofFootgunlisted on 3 directories

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

First seen 19 Oct 2026. Evidence as of 16 Nov 2026.

4
Tools
From an anonymous probe
1
Source listings
Each with its own history
13
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
confirm_trapAfter you hit or avoid a trap returned by lookup_traps or search_traps, record whether it is still true. Confirmations raise a trap's trust score and disputes lower it; several disputes send it back for review. One vote per trap per 30 days. Needs a free API key.Changes data
file_trapDraft 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.Changes data
lookup_trapsCall before writing code against a third-party API, platform, or AI tool. Returns up to 10 verified, dated failure modes for that provider, each with symptoms, cause, fix, a code example and the date it was last checked. Use search_traps instead when you already have an error message.Read-only
search_trapsCall when a call to a third-party service fails or behaves unexpectedly. Paste the error text. Returns up to 5 verified traps whose symptoms match it, closest first, each with cause and fix. Returns nothing when no trap matches closely. Use lookup_traps instead before writing code.Read-only

Change history

  1. search_traps: input schema changed
  2. search_traps: description changed (+"fails or behaves unexpectedly." +"up to 5" +"whose symptoms match it, closest first, each")
  3. lookup_traps: input schema changed
  4. lookup_traps: description changed (+"up to 10" +"for that provider, each" +"symptoms, cause, fix, a code example and the date it was last checked. Use search_traps instead when you already have an error message.")
  5. file_trap: input schema changed
  6. confirm_trap: input schema changed
  7. confirm_trap: description changed (+"After you hit or avoid" +"returned by lookup_traps or search_traps, record whether it" +"true. Confirmations raise a trap's trust score")
  8. Description changed (registry)
  9. file_trap: description changed (+"key. Public" +"are checked automatically against official sources and published only when an official source confirms them." +"reviewer can still act on any filing. Citing")
  10. file_trap: input schema changed (+visibility)
  11. file_trap: description changed (+"Private by default with a Pro or Team key; public filings enter the review queue." +"public trap is reviewed by a" +"Set visibility to public to submit to the public registry.")
  12. server instructions changed (+"With a Pro or Team key, file_trap saves to the caller's private space by default and those traps are served first. Use visibility public to submit a trap to the public registry. When the user asks to import their lessons, follow the import steps on their account page.")
  13. Listed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registrycom.getfootgun/footgun19 Oct 202616 Nov 20262