AI Brand Visibility Tracker vs Tin
A side-by-side look at the AI Brand Visibility Tracker and Tin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI Brand Visibility Tracker for marketing work; choose Tin for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose AI Brand Visibility Tracker when
- You need dedicated capabilities in the Marketing domain.
Choose Tin when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A AI Brand Visibility Tracker | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 37/100 · Fair | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 264 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AI Brand Visibility Tracker | View Tin |
Tools & capabilities
AI Brand Visibility Tracker tools
No tool names declared yet. Check the project README from the listing page.
Tin 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.
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}