DABLOCK AI Visibility Index
Measured share of answer for 24 crypto and Web3 brands.
Connector by dablock.aiOfficial · Domain verified by the MCP Registry
Install
Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install connector/dablock-ai-visibility-index
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Remote endpoint
https://dablock.ai/mcpRemote (HTTP)
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 5 read · 0 write · 0 deleteRead-only
- Secrets
- None asked for
- Install scripts
- Nothing to install (hosted)
- Runs as
- Hosted (remote endpoint)
Tools by what they do 5
From the running server's own tool list (tools/list) on Oct 25, 2026.
Read 5 · Look things up without changing anything.
get_brand_visibilityget_historyget_methodologyget_visibility_indexlist_tracked_brands
Network hosts it talks to 1
dablock.ai· found in remote endpoint, install command
Tools (5)
As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].
get_brand_visibilityLook up one brandread-onlyOne brand's standing in the current DABLOCK release: share of answer per engine, rank, quadrant, how many panel prompts name it, and which ones. Use this when a specific brand is named. Takes a slug, not a display name — call list_tracked_brands first if you are unsure, or read the slug from get_visibility_index. An unknown slug is not a failure to hide: the error names every valid slug, so a second attempt can succeed. A brand absent from the index has not been measured at all, which is different from a measured zero. Only crypto/Web3 brands are tracked. For the field as a whole use get_vis…
get_historyFull measurement time seriesread-onlyEvery DABLOCK release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt …
get_methodologyHow the index is measuredread-onlyThe rules behind every figure this server returns: the exact prompt panel and its version, which engines were measured, how share of answer is scored and rounded, the resolution of the scale in percentage points, and the editorial firewall and ownership disclosure. Call this before quoting a number as evidence, before comparing two releases, or whenever a user asks how the measurement was made or who publishes it. It is the only tool that tells you how much of a difference is meaningful, which is what stops a one-step wobble being reported as a movement. It returns rules, not figures — no br…
get_visibility_indexDABLOCK AI Visibility Index — full tableread-onlyThe whole current release in one call: every tracked brand in crypto/Web3 with its rank, share of answer overall and per engine, commercial intent and quadrant. Share of answer is the percentage of a fixed panel of category buyer prompts in which an engine names the brand. Use this when the question is about the field — who leads, who is absent, how the category looks. It is one response of roughly 8 KB for 24 brands, so prefer it over calling get_brand_visibility repeatedly. Do NOT use it for one named brand (get_brand_visibility is the direct answer), for movement over time (get_history ho…
list_tracked_brandsList tracked brands and slugsread-onlyThe names and slugs of every brand in the DABLOCK index — a lookup table, nothing else. No scores, no ranks. Use it for two things: to turn a brand name into the slug get_brand_visibility needs, and to answer whether a brand is tracked at all. Do NOT use it when you want figures — get_visibility_index returns the same brands with their full measurements in a single call, so calling this one first is a wasted round trip. Absence here means the brand is not measured, not that it scores zero. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche. Re-measured weekly, so…
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit
- Oct 20, 2026 (8 days ago)
- Last release
- Aug 6, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
ai.dablock/visibility-index- Version
- 1.0.1
- Auth
- Auth not stated
- License
- MIT
- Repository
- github.com/creanlab/ai-visibility-index
- Website
- dablock.ai/
- First seen
- Oct 24, 2026
- Last checked
- Oct 25, 2026
Cite this page
DABLOCK AI Visibility Index MCP server. Agent Mart. https://agentmart.dev/connectors/dablock-ai-visibility-index (last updated 2026-10-25)