# Footgun (remote · getfootgun.com)

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

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `getfootgun.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-getfootgun-footgun/api-mcp.md), [page](https://verifymcp.io/servers/com-getfootgun-footgun/api-mcp)

## Channel facts

- Endpoint: `https://getfootgun.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-getfootgun-footgun": {
      "url": "https://getfootgun.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getfootgun-footgun": {
      "type": "http",
      "url": "https://getfootgun.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-getfootgun-footgun]
url = "https://getfootgun.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getfootgun-footgun": {
      "type": "remote",
      "url": "https://getfootgun.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getfootgun-footgun --url 'https://getfootgun.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-getfootgun-footgun:
    url: "https://getfootgun.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-getfootgun-footgun": {
      "Transport": "http",
      "Url": "https://getfootgun.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getfootgun-footgun -t streamable-http -u 'https://getfootgun.com/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +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.

### 2026-11-03 (score 79, +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.

### 2026-11-01 (score 78, +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.

### 2026-10-30 (score 77, +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.

### 2026-10-28 (score 76, +5)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: fair → excellent
- [cosmetic] “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”

### 2026-10-26 (score 71, +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.

### 2026-10-24 (score 70, +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.

### 2026-10-21 (score 69, +1)

- [security] Tool “file_trap” rewrote its description, which is the text the model reads

## MCP tools (4)

### `lookup_traps` (~197 tokens)

Look up traps for a provider

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.

Input parameters:

- `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, required): 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.

### `search_traps` (~142 tokens)

Search traps by error text

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.

Input parameters:

- `error_text` (string, required): 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.

### `file_trap` (~317 tokens)

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.

Input parameters:

- `affected` (string, required): Which versions, plans or dates are affected.
- `apply` (string, required): A short code or command example of the fix.
- `cause` (string, required): Why it happens.
- `fix` (string, required): What to change, in plain words.
- `provider` (string, required): The service, by slug or common name, e.g. "stripe".
- `sources` (array): Official documentation or changelog URLs that confirm it.
- `surface_name` (string, required): The specific endpoint, package, command or screen, e.g. "webhooks.constructEvent".
- `surface_type` (string, required): Which kind of surface broke: api, sdk, ui, billing, infra, or tool (CLIs and AI coding tools).
- `symptoms` (array, required): Exact error messages or observed behavior, one per item. Leave out secrets and personal data.
- `tags` (array): Optional short keywords.
- `title` (string, required): 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).

### `confirm_trap` (~168 tokens)

Confirm or dispute a trap

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.

Input parameters:

- `hours_lost` (number): Optional hours the trap cost before the fix was found.
- `still_true` (boolean, required): true if the trap happened as described, false if it no longer happens.
- `trap_id` (string, required): 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".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-getfootgun-footgun/api-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 68
- 2026-10-19: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://getfootgun.com/api/mcp
- Repository: https://github.com/GetFootgun/footgun
- Website: https://getfootgun.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-getfootgun-footgun/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getfootgun-footgun/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-getfootgun-footgun/api-mcp