DigestSEO mcp Geo — AI Visibility MCP Server vs Tin
A side-by-side look at the DigestSEO mcp Geo — AI Visibility MCP Server 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 DigestSEO mcp Geo — AI Visibility MCP Server for marketing work as a local process; 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?
Choose DigestSEO mcp Geo — AI Visibility MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, SERPAPI_API_KEY. - You want tools like
visibility.check, visibility.history, visibility.compare.
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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 63/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | OPENAI_API_KEYANTHROPIC_API_KEYGEMINI_API_KEYPERPLEXITY_API_KEYXAI_API_KEYSERPAPI_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 38 | 264 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View DigestSEO mcp Geo — AI Visibility MCP Server | View Tin |
Tools & capabilities
DigestSEO mcp Geo — AI Visibility MCP Server tools 6
visibility.checkLatest AI visibility snapshot across all configured engines for a tracked brand, with per-engine scores, winning prompts, and losing prompts.visibility.historyTime-series history of overall and per-engine visibility, bucketed daily or weekly.visibility.compareShare-of-voice comparison against competitor domains, with prompts you win and prompts they win.visibility.citationsThe actual citation events — prompt, engine, response excerpt, citation type, brand URL when present.visibility.content_gapsPrioritized Claude-Haiku-generated content recommendations targeting your losing prompts.visibility.refreshManually trigger a fresh scan across every engine whose API key is set.
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.
DigestSEO mcp Geo — AI Visibility MCP Server
{
"mcpServers": {
"digestseo-mcp-geo-ai-visibility-mcp-server": {
"command": "npx",
"args": [
"-y",
"@digestseo/mcp-geo"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
"SERPAPI_API_KEY": "YOUR_SERPAPI_API_KEY_HERE"
}
}
}
}
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}
Frequently asked questions
DigestSEO mcp Geo — AI Visibility MCP Server is categorized under Marketing and uses a local stdio subprocess. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick DigestSEO mcp Geo — AI Visibility MCP Server for marketing work and Tin for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
DigestSEO mcp Geo — AI Visibility MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Tin 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 digestseo-mcp-geo-ai-visibility-mcp-server and tin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DigestSEO mcp Geo — AI Visibility MCP Server has a quality signal of 63/100 (Good) with 4 views, 0 installs and 38 GitHub stars. Tin has 45/100 (Fair) with 1 views, 0 installs and 264 GitHub stars.