Log inSubmit server
Footgun logo

Footgun

Checks dated API failure modes before coding and helps agents diagnose, file, and verify third-party integration traps.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Footgun

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "footgun": {
      "command": "npx",
      "args": [
        "-y",
        "@getfootgun/footgun"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 11/10/2026, 9:00:31 PM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://getfootgun.com/api/mcp
We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @getfootgun/footgun

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 3d ago.

Overview

Footgun MCP server gives coding agents access to a dated registry of verified ways APIs, platforms, and AI tools fail in practice. Its lookup_traps tool provides provider-specific warnings before implementation, while search_traps matches unexpected errors to likely causes and fixes. Agents can also file newly resolved failures and confirm or dispute existing traps. Use Footgun when working with changing third-party services or investigating behavior that official documentation does not explain.

Use cases

  • Check known provider traps before implementing an API integration
  • Match a failed third-party call to a documented cause and fix
  • Submit a newly resolved integration failure for review
  • Confirm or dispute a trap after testing it

Key features

  • Dated, verified provider failure modes
  • Error-message trap search
  • Trap filing with official-source review
  • Trust-score confirmations and disputes
  • Streamable HTTP MCP endpoint
  • Code examples attached to trap records

Tools4

What Footgun lets your agent do. Expand a tool for its parameters.

Verified live~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 20d

What it can do

From the 4 tools this server returned when we ran it.

Handles credentials · 2Read-only tools · 4
Tool definitions changed on 2026-10-29. Review them if you approved this server earlier.

Observed 2026-10-29 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @getfootgun/footgun (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.1kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed4Callable tools this server registers over MCP.

How Footgun works

What Footgun does

Footgun provides an MCP-accessible registry of verified integration failures. Entries cover issues such as silent deprecations, ineffective settings, and service limits that may not be obvious from normal API documentation. Each trap can include observed symptoms, an explanation of the cause, a corrective code example, the date it was last checked, and a trust score.

The service is intended for two points in a development workflow: before writing code against a provider, and after an integration behaves unexpectedly. Its data is exported from the Footgun registry, where public traps can be added, confirmed, disputed, reviewed, or retired.

How it works

Use lookup_traps with the name of a third-party API, platform, or AI tool before implementing an integration. It returns up to 10 matching failure modes, including symptoms, causes, fixes, examples, and verification dates. When an existing call fails, send the error text to search_traps; it returns up to five closely matching traps, ordered by relevance, or no results when the match is weak.

After resolving a previously unknown failure, file_trap can create a draft entry. New public filings are checked against official sources, and publication requires confirmation from an official source. Reviewers can still act on a filing while it is being evaluated. Citing provider documentation or changelogs makes a filing easier to verify.

confirm_trap records whether a returned trap still applies or should be disputed. Confirmations increase its trust score, while multiple disputes can send it back for review. A trap can be voted on once every 30 days.

Setup and configuration

The hosted MCP endpoint uses streamable HTTP:

text
https://getfootgun.com/api/mcp

For Claude Code, install the plugin with:

text
/plugin marketplace add getfootgun/footgun
/plugin install footgun@footgun

Other MCP clients can connect their streamable-HTTP configuration to the endpoint. Add Authorization: Bearer <your key> when using authenticated filing or confirmation features. Lookups and basic filing work without an account; confirming traps requires a free API key, while private filing requires a Pro or Team key.

The repository also includes a command-line scanner distributed as @getfootgun/footgun. Run npx @getfootgun/footgun scan [path] with Node.js 20 or later. The scanner supports JSON output and CI failure thresholds, but it is separate from the four MCP tools described here.

Tools and capabilities

  • lookup_traps: Find up to 10 dated, verified traps for a provider before coding.
  • search_traps: Match an error message to as many as five likely traps.
  • file_trap: Submit a newly discovered failure for review or verification.
  • confirm_trap: Confirm or dispute a trap and influence its trust score.
  • Streamable-HTTP access through the hosted MCP endpoint.
  • Public trap records containing verification dates and trust scores.

Limitations and notes

Results depend on the registry containing a close match. search_traps intentionally returns nothing when no trap matches closely, so an empty response is not a diagnosis of the underlying failure. Public filings are not published until an official source confirms them, and dashboard-only issues may require a manual check.

The separate Claude Code scanner examines exact package versions locally. It sends rule downloads and an anonymous finding count, not project source code; watch mode sends package metadata and finding locations rather than code. Trap data is licensed under CC BY 4.0, while the plugin files use the MIT license.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Footgun

Footgun is an MCP server that connects coding agents to a dated registry of verified API and platform failure modes. Its main tools look up traps before coding, search error messages after failures, file newly discovered traps, and confirm or dispute existing traps. It helps agents account for behavior that documentation may omit.

Install it in Claude Code with `/plugin marketplace add getfootgun/footgun` followed by `/plugin install footgun@footgun`. For other MCP clients, connect to `https://getfootgun.com/api/mcp` using streamable HTTP. Add a bearer API key when the client needs authenticated filing or confirmation features.

Yes, Cursor can connect to Footgun through its streamable HTTP MCP endpoint. Point Cursor at `https://getfootgun.com/api/mcp`; use an `Authorization: Bearer <your key>` header for filing or confirming traps that require authentication.

No, lookups and basic trap filing work without an account. Confirming a trap requires a free API key, and private filing requires a Pro or Team key. Clients should send the key as a bearer token when using authenticated features.

Call `search_traps` with the error text from the failed third-party call. Footgun returns up to five verified traps whose symptoms most closely match the message, ordered by relevance, and returns no results when the match is not close enough.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFootgun AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/footgun?style=directory)](https://allmcps.com/mcp/footgun)
HTML Embed
<a href="https://allmcps.com/mcp/footgun"><img src="https://allmcps.com/api/badge/footgun?style=directory" alt="Footgun on AllMCPs" /></a>