TOP GUN GEO MCP Server

Brand visibility auditing across LLMs, AI search, and answer engines with GEO reports and scores. The top gun geo mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

TOP GUN GEO-Lens measures how visible a brand is across the sources that power AI answers: Brave AI Search, Exa neural search, and LLM-indexed content. It returns a scored report with citations, index status, and concrete GEO (Generative Engine Optimization) recommendations.

Configuration

You will need 6 environment variables: STRIPE_SECRET_KEY, STRIPE_PAYMENT_URL, STRIPE_QUICK_CHECK_PAYMENT_URL, BRAVE_SEARCH_API_KEY, EXA_API_KEY, USDC_WALLET_ADDRESS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by Spacemandomains; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against TOP GUN GEO's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the top gun geo mcp server does with a few real requests.