trackian-mcp-server vs DABLOCK AI Visibility Index
trackian-mcp-server is a plugin bundle for AI coding tools published by trackian. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). DABLOCK AI Visibility Index is an MCP server published by dablock.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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 | trackian-mcp-server | DABLOCK AI Visibility Index |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (dablock.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/trackian/claude-plugin | github.com/creanlab/ai-visibility-index |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
trackian-mcp-server
Trackian MCP Plugin for Claude Code This plugin connects Claude Code to your Trackian Marketing Analytics data via the Model Context Protocol (MCP). Investigate marketing anomalies and query your analytics data from Claude Code. Trackian connects Claude Code to your marketing data — GA4, Facebook Ads, Google Ads, Search Console, and your data warehouse. Ask Claude to investigate anomalies, generate, channel reports, or run deep analyses the way a data analyst would.
DABLOCK AI Visibility Index
Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.
How to run each
trackian-mcp-server As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install trackian-mcp-server@claude-community
DABLOCK AI Visibility Index As a remote MCP server
claude mcp add --transport http visibility-index https://dablock.ai/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only DABLOCK AI Visibility Index 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
The marketplaces of DABLOCK AI Visibility Index publish no settings it asks for, so we do not compare settings.
What it can do: trackian-mcp-server · What it can do: DABLOCK AI Visibility Index · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.