Search / ai.dablock/visibility-index
protogridR0· no sign-inMeasured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.
v1.0.1 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"visibility-index": {
"type": "http",
"url": "https://dablock.ai/mcp"
}
}
}claude mcp add --transport http visibility-index https://dablock.ai/mcp[mcp_servers.visibility-index]
url = "https://dablock.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"visibility-index": {
"type": "remote",
"url": "https://dablock.ai/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"visibility-index": {
"type": "http",
"url": "https://dablock.ai/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=visibility-index&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZGFibG9jay5haS9tY3AifQ%3D%3D"
}{
"servers": {
"visibility-index": {
"type": "http",
"url": "https://dablock.ai/mcp"
}
}
}{
"mcpServers": {
"visibility-index": {
"httpUrl": "https://dablock.ai/mcp"
}
}
}extensions:
"visibility-index":
enabled: true
name: "visibility-index"
type: streamable_http
uri: "https://dablock.ai/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length3 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations5 of 5 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 1,545 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-95% ~updated-75d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://dablock.ai/mcp streamable-http | none | yes | 95% | 300 ms | 2025-06-18 | 2026-10-19 |
get_brand_visibilityread-only | 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. |
get_historyread-only | 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. |
get_methodologyread-only | 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. |
get_visibility_indexread-only | 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. |
list_tracked_brandsread-only | 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. |
Schemas: list_tools.
1 other active names share this repository: ai.dabyte/visibility-index
{
"name": "ai.dablock/visibility-index",
"icons": [
{
"src": "https://dablock.ai/favicon.svg",
"sizes": [
"any"
],
"mimeType": "image/svg+xml"
}
],
"title": "DABLOCK AI Visibility Index",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://dablock.ai/mcp",
"type": "streamable-http"
}
],
"version": "1.0.1",
"repository": {
"url": "https://github.com/creanlab/ai-visibility-index",
"source": "github"
},
"websiteUrl": "https://dablock.ai/",
"description": "Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site."
}