Footgun
REMOTE · GETFOOTGUN.COM
Dated, verified API breakages for coding agents, plus a local scan for them in your existing code.
Available components
Last scanned (4 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 960 tokens (~240/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +5
- Tool “confirm_trap” rewrote its description, which is the text the model reads security
- Tool “lookup_traps” rewrote its description, which is the text the model reads security
- Tool “search_traps” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → excellent functional
- “confirm_trap” reworded the description of “hours_lost” cosmetic
- “confirm_trap” reworded the description of “still_true” cosmetic
- “confirm_trap” reworded the description of “trap_id” cosmetic
- “confirm_trap” reworded the description of “version_seen” cosmetic
- “file_trap” reworded the description of “affected” cosmetic
- “file_trap” reworded the description of “apply” cosmetic
- “file_trap” reworded the description of “cause” cosmetic
- “file_trap” reworded the description of “fix” cosmetic
- “file_trap” reworded the description of “provider” cosmetic
- “file_trap” reworded the description of “sources” cosmetic
- “file_trap” reworded the description of “surface_name” cosmetic
- “file_trap” reworded the description of “surface_type” cosmetic
- “file_trap” reworded the description of “symptoms” cosmetic
- “file_trap” reworded the description of “tags” cosmetic
- “file_trap” reworded the description of “title” cosmetic
- “file_trap” reworded the description of “visibility” cosmetic
- “lookup_traps” reworded the description of “context” cosmetic
- “lookup_traps” reworded the description of “include_stale” cosmetic
- “lookup_traps” reworded the description of “provider” cosmetic
- “lookup_traps” reworded the description of “surface” cosmetic
- “search_traps” reworded the description of “error_text” cosmetic
- “search_traps” reworded the description of “include_stale” cosmetic
- “search_traps” reworded the description of “provider” cosmetic
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
- Tool “file_trap” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://getfootgun.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getfootgun.com | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 5b18aae129bb9ad796bd3a2af84146a63da |
| SANs: getfootgun.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of getfootgun.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getfootgun.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getfootgun.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://getfootgun.com/api/mcp | HTTPS enforced | 308 | https://getfootgun.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
confirm_trap Confirm or dispute a trap ~168
After 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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours_lost | number | – | Optional hours the trap cost before the fix was found. |
| still_true | boolean | yes | true if the trap happened as described, false if it no longer happens. |
| trap_id | string | yes | The trap id from a lookup or search result, e.g. "fg-0158". |
| version_seen | string | – | Optional SDK, API or tool version where you saw it, e.g. "stripe-node 22.3.0". |
No output schema declared.
No examples provided.
file_trap File a new trap ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| affected | string | yes | Which versions, plans or dates are affected. |
| apply | string | yes | A short code or command example of the fix. |
| cause | string | yes | Why it happens. |
| fix | string | yes | What to change, in plain words. |
| provider | string | yes | The service, by slug or common name, e.g. "stripe". |
| sources | array | – | Official documentation or changelog URLs that confirm it. |
| surface_name | string | yes | The specific endpoint, package, command or screen, e.g. "webhooks.constructEvent". |
| surface_type | string | yes | Which kind of surface broke: api, sdk, ui, billing, infra, or tool (CLIs and AI coding tools). |
| symptoms | array | yes | Exact error messages or observed behavior, one per item. Leave out secrets and personal data. |
| tags | array | – | Optional short keywords. |
| title | string | yes | One line naming what goes wrong, as a developer would search for it. |
| visibility | string | – | public submits to the shared registry; private keeps it in your team's space (Pro or Team key). |
No output schema declared.
No examples provided.
lookup_traps Look up traps for a provider ~197
Call 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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional one-line description of the task, e.g. "verify webhook signatures in Next.js". Ranks the most relevant traps first. |
| include_stale | boolean | – | Also return traps not re-checked recently. Default false. |
| provider | string | yes | The service, by slug or common name, e.g. "stripe", "supabase", "github-actions", "openai api". |
| surface | string | – | Optional part of the service you are working on, e.g. "webhooks" or "image generation". Ranks matching traps first; never filters others out. |
No output schema declared.
No examples provided.
search_traps Search traps by error text ~142
Call 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.
| Name | Type | Req | Description |
|---|---|---|---|
| error_text | string | yes | The error message or unexpected output, as shown. Known key and secret formats are redacted before matching. |
| include_stale | boolean | – | Also match traps not re-checked recently. Default false. |
| provider | string | – | Optional service slug or name to search within, e.g. "stripe". Omit to search every provider. |
No output schema declared.
No examples provided.
How do I install the Footgun MCP server?
Footgun is a hosted endpoint at https://getfootgun.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · getfootgun.com
claude mcp add --transport http com-getfootgun-footgun 'https://getfootgun.com/api/mcp'
What is the Footgun MCP server?
Footgun is an MCP server listed in the public MCP registry as com.getfootgun/footgun. Dated, verified API breakages for coding agents, plus a local scan for them in your existing code. This page covers its hosted endpoint (https://getfootgun.com/api/mcp).
Is the Footgun MCP server safe to use?
Footgun scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Footgun MCP server expose?
Footgun exposes 4 tools: lookup_traps, search_traps, file_trap, confirm_trap. Their descriptions and schemas cost roughly 824 tokens of context every time the server is loaded.
Does the Footgun MCP server require authentication?
No. We connected to Footgun without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Footgun MCP server still maintained?
Footgun is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.