DABYTE AI Visibility Index MCP server
ai.dabyte/visibility-indexdabyte.aistreamable-httpv1.0.1Scanned
Measured share of answer for 20 SaaS brands. An open dataset, not an audit of your site.
5 tools: 5 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DABYTE AI Visibility Index MCP server can do
The DABYTE AI Visibility Index MCP server is published by dabyte.ai, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (list_tracked_brands).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
get_brand_visibilityOne brand's standing in the current DABYTE release: share of answer per engine, rank, quadrant, how many panel prompts name it, and which ones.No findings
Why it is in this group
- The name "get_brand_visibility" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Look up one brand
get_historyEvery 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.No findings
Why it is in this group
- The name "get_history" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Full measurement time series
get_methodologyThe 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…No findings
Why it is in this group
- The name "get_methodology" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: How the index is measured
get_visibility_indexThe 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.No findings
Why it is in this group
- The name "get_visibility_index" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: DABYTE AI Visibility Index — full table
list_tracked_brandsThe names and slugs of every brand in the DABYTE index — a lookup table, nothing else.Reads private dataNo findings
Why it is in this group
- The name "list_tracked_brands" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: List tracked brands and slugs
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http visibility-index https://dabyte.ai/mcpclaude mcp add --transport http visibility-index https://dabyte.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__visibility-index__get_visibility_index",
"mcp__visibility-index__get_brand_visibility",
"mcp__visibility-index__list_tracked_brands",
"mcp__visibility-index__get_history",
"mcp__visibility-index__get_methodology"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as visibility-index. Review it before you use it.
Capability tags behind 1 rule
- mcp__visibility-index__list_tracked_brands private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.dabyte/visibility-index/verify?hash=5667103641d2afa384f7cbbbab0128f4aff11eaff1648b445bb2d3ecb3a884e0" | jq -e '.changed == false'Pinned hash 5667103641d2, from Nov 10, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.dabyte/visibility-index/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.dabyte/visibility-index)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:41 UTC.
DABYTE AI Visibility Index MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DABYTE AI Visibility Index MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the DABYTE AI Visibility Index MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the DABYTE AI Visibility Index MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DABYTE AI Visibility Index MCP server have?
- 5 tools: 5 read. get_visibility_index, get_brand_visibility, list_tracked_brands, get_history and get_methodology.
Does the DABYTE AI Visibility Index MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the DABYTE AI Visibility Index MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DABYTE AI Visibility Index MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.