Brand Intelligence MCP Server

If you already use Brand Intelligence MCP, the brand intelligence mcp mcp server is the piece that lets your assistant work with it directly. Domain & brand intelligence: company enrichment, tech stack detection, brand research.

What the server does

On a query for a domain that's missing or stale (>7 days), the server enriches live and caches the result in its own standalone Supabase project; otherwise it returns the cache. A daily background task refreshes stale rows.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• domain_profile — $0.02
• tech_stack — $0.01
• domain_age — free
• batch_enrich — $0.01/domain (min $0.05)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

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. Brand Intelligence MCP's toolset — domain_profile, tech_stack, domain_age and 1 more — is a fair guide to whether it matches your workflow. It is maintained by FoundryNet; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.