DABYTE AI Visibility Index
Server Details
Measured share of answer for 20 SaaS brands. An open dataset, not an audit of your site.
- 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
Scored across 5 tools
Each tool targets a clearly distinct access pattern: current single brand, current full index, historical series, methodology, and brand lookup. The descriptions explicitly cross-reference the others and state when not to use a given tool, so an agent should have no trouble selecting the right one.
All tool names follow a consistent verb_noun pattern using lowercase snake_case: get_brand_visibility, get_history, get_methodology, get_visibility_index, and list_tracked_brands. The one list_ prefix is a natural fit for a lookup-table tool and does not break the overall convention.
Five tools is well-scoped for a read-only visibility index server. Each tool covers a distinct necessary capability without redundancy or bloat.
The domain is fully covered: brand lookup, current single-brand data, current full index, historical time series, and the methodology needed to interpret figures correctly. There are no obvious dead ends or missing operations for the stated purpose.
Available Tools
5 toolsget_brand_visibilityLook up one brandARead-onlyIdempotentInspect
One brand's standing in the current DABYTE 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 SaaS & AI tools 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 dabyte.ai when quoting a number.
Inputs: slug (required). Returns: rank, slug, brand, engines, +9 more
get_historyFull measurement time seriesARead-onlyIdempotentInspect
Every DABYTE 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 dabyte.ai when quoting a number.
Inputs: no named parameters. Returns: series, measurements
get_methodologyHow the index is measuredARead-onlyIdempotentInspect
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://dabyte.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 dabyte.ai when quoting a number.
Inputs: no named parameters. Returns: engines, license, scoring, publisher, +5 more
get_visibility_indexDABYTE AI Visibility Index — full tableARead-onlyIdempotentInspect
The whole current release in one call: every tracked brand in SaaS & AI tools 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 20 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 SaaS & AI tools only; the sibling index at dablock.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 dabyte.ai when quoting a number.
Inputs: no named parameters. Returns: engines, entries, measured_at, niche_title, +1 more
list_tracked_brandsList tracked brands and slugsARead-onlyIdempotentInspect
The names and slugs of every brand in the DABYTE 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 SaaS & AI tools only; the sibling index at dablock.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 dabyte.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
Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.
AI visibility: which buyer questions name your brand in ChatGPT, Perplexity, Claude, AI Overviews.
Diagnose brand visibility in AI answers (ChatGPT, Perplexity, AI Overviews). Free + paid audits.
How often ChatGPT, Perplexity, Gemini and Claude mention and cite your brand vs competitors.
Related MCP Servers
- AlicenseAqualityDmaintenanceAudit 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.5204 npmMIT
- AlicenseAqualityDmaintenanceTrack brand visibility across ChatGPT, Perplexity, Claude, and Gemini.6277 npm11MIT
- AlicenseBqualityCmaintenanceAdvanced content gap analysis using Query Decomposition and Keyword Fan-Out (Google's patented methodology). Tells you exactly what user queries your content covers - and what it misses. Built on academic research because I needed to understand how AI search engines actually evaluate content.1141 npm15Apache 2.0
- AlicenseAqualityBmaintenanceAI visibility and SEO data for AI agents. Check whether ChatGPT, Claude, Perplexity and Gemini mention your brand and which sources they cite, plus keyword volume and Google Trends.29943 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.