Skip to main content
Glama

DABLOCK AI Visibility Index

Server Details

Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
creanlab/ai-visibility-index
GitHub Stars
0
Server Listing
ai-visibility-index
ChatGPT
–
Claude
–

TDQS

A4.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct question: current field-level figures, current single-brand figures, history over time, methodology, and slug lookup. The descriptions explicitly cross-reference the other tools and state when not to use each one, so an agent should rarely misfire.

Naming Consistency5/5

All tool names follow a clear verb_noun snake_case pattern: get_brand_visibility, get_history, get_methodology, get_visibility_index, list_tracked_brands. The single list_ verb is conventional for a lookup operation and does not break the pattern.

Tool Count5/5

Five tools map cleanly to the natural operations on this read-only dataset: current index, one brand, history, methodology, and slug lookup. The server is tightly scoped and no tool feels redundant.

Completeness5/5

For a read-only measurement index, the surface is complete: agents can resolve slugs, query current figures at field or brand level, trace history, and understand methodology before citing numbers. There are no obvious dead ends or missing operations.

Available Tools

5 tools
get_brand_visibilityLook up one brandA
Read-onlyIdempotent
Inspect

One 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_visibility_index; for this brand over time, get_history.

Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

Inputs: slug (required). Returns: rank, slug, brand, engines, +9 more

get_historyFull measurement time seriesA
Read-onlyIdempotent
Inspect

Every 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 runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index.

Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

Inputs: no named parameters. Returns: series, measurements

get_methodologyHow the index is measuredA
Read-onlyIdempotent
Inspect

The 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 brand appears in the response. For figures use get_visibility_index or get_brand_visibility; for the series, get_history. The panel is public and frozen between releases, so every published number can be recomputed by a third party from the archive at https://dablock.ai/archive/.

Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

Inputs: no named parameters. Returns: engines, license, scoring, publisher, +5 more

get_visibility_indexDABLOCK AI Visibility Index — full tableA
Read-onlyIdempotent
Inspect

The 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 holds the series; a single release cannot show a trend), or to audit a website's own AI visibility — this is a measured dataset about third-party brands, not a site audit. Covers crypto/Web3 only; the sibling index at dabyte.ai covers the other niche.

Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

Inputs: no named parameters. Returns: engines, entries, measured_at, niche_title, +1 more

list_tracked_brandsList tracked brands and slugsA
Read-onlyIdempotent
Inspect

The 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 the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dablock.ai when quoting a number.

Inputs: no named parameters. Returns: brands

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Audit your brand's visibility across ChatGPT, Perplexity, Claude, and Google AI - get citation rates, AEO health scores, content gap analysis, and a 9-page content suite to rank in AI-generated answers.
      5
      204 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Find out how AI assistants and search engines talk about your brand. Ask how often ChatGPT, Perplexity and Google's AI answers mention you, where you rank, how positive those mentions are, which sites they cite, and how you compare with competitors. Your assistant can also set up and adjust the monitoring for you, showing a preview and asking before anything that deletes data or uses up your plan.
      68
      124 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.