digestseo-geo vs de.auracite/ai-visibility
digestseo-geo is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑11.
digestseo-geo is a plugin bundle for AI coding tools published by akzar1el. No marketplace we read lists it any more. de.auracite/ai-visibility is an MCP server published by auracite.de. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace akzar1el/mcp-geo | Removed on 2026-11-11 Version: 0.3.31 Forks (GitHub): 2 Stars (GitHub): 40 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | digestseo-geono longer listed · | de.auracite/ai-visibility |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 40 | 0 |
| Forks (GitHub) (differs) | 2 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@digestseo/mcp-geo) | Remote server (auracite.de/mcp/rpc) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/akzar1el/mcp-geo | github.com/g5317/auracite-claude-plugins |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 23 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of digestseo-geo
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Track how ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews cite your brand.
-
Wrenfield AI Search Visibility
Track brand mentions, share of voice and cited URLs in ChatGPT, Perplexity, Gemini and AI Overviews.
-
Track brand visibility, citations, prompts & missing sources across ChatGPT, Perplexity, Gemini.
-
AI Visibility Tracker (via Apify)
AI visibility for agents: is a brand mentioned and cited by Gemini, Claude and Google AI Overviews?
-
AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers.
-
CitedOrNot - AI Search Visibility
AI search visibility for your brand: which AI engines name it, who wins instead, what to publish.
What each says it does
digestseo-geo
Track brand citations and AI visibility across ChatGPT, Claude, Perplexity, Gemini, Grok, Google AI Overviews, and Google AI Mode.
de.auracite/ai-visibility
Track how ChatGPT, Gemini & Perplexity mention, rank & cite your brand. AuraCite account required.
How to run each
digestseo-geo
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
de.auracite/ai-visibility As a remote MCP server
claude mcp add --transport http ai-visibility https://auracite.de/mcp/rpc
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only de.auracite/ai-visibility has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: digestseo-geo · What it can do: de.auracite/ai-visibility · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.