AI Brand Visibility Tracker vs CiteHawk

A side-by-side look at the AI Brand Visibility Tracker and CiteHawk MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

A
AI Brand Visibility TrackerMarketing
Check if ChatGPT, Perplexity & Gemini mention or cite a brand. Share of voice + GEO/AEO tracking.37FairAuth: not declared
C
CiteHawkMarketing
AI-search visibility (GEO) analytics: brand scores, competitor rankings, recommendations, evidence.42FairAuth: not declared

Verdict: choose AI Brand Visibility Tracker for marketing work; choose CiteHawk for marketing. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose AI Brand Visibility Tracker when

  • You need dedicated capabilities in the Marketing domain.
Explore AI Brand Visibility Tracker

C
Choose CiteHawk when

  • You need dedicated capabilities in the Marketing domain.
Explore CiteHawk

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
AI Brand Visibility Tracker
C
CiteHawk
CategoryMarketingMarketing
Quality signal37/100 · Fair42/100 · Fair
Install commandNot confirmed yetNot confirmed yet
Transport——
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars——
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

AI Brand Visibility Tracker tools

No tool names declared yet. Check the project README from the listing page.

CiteHawk tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

AI Brand Visibility Tracker

No confirmed install command for AI Brand Visibility Tracker yet — follow the setup steps linked from its listing page rather than a guessed package name.

CiteHawk

No confirmed install command for CiteHawk yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

AI Brand Visibility Tracker is categorized under Marketing and uses an install path we have not confirmed yet. CiteHawk belongs to Marketing and uses an install path we have not confirmed yet. Pick AI Brand Visibility Tracker for marketing work and CiteHawk for marketing.

Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.

AI Brand Visibility Tracker has no declared pricing — check the project's own site. CiteHawk has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ai-brand-visibility-tracker and citehawk as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, AI Brand Visibility Tracker has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. CiteHawk has 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.