DABLOCK AI Visibility Index
REMOTE · DABLOCK.AI · SCANNED SEP 20
Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1206 tokens (~241/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the DABLOCK AI Visibility Index MCP server?
DABLOCK AI Visibility Index is a hosted endpoint at https://dablock.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · dablock.ai
claude mcp add --transport http ai-dablock-visibility-index 'https://dablock.ai/mcp'
{
"mcpServers": {
"ai-dablock-visibility-index": {
"url": "https://dablock.ai/mcp"
}
}
} {
"servers": {
"ai-dablock-visibility-index": {
"type": "http",
"url": "https://dablock.ai/mcp"
}
}
} [mcp_servers.ai-dablock-visibility-index] url = "https://dablock.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-dablock-visibility-index": {
"type": "remote",
"url": "https://dablock.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-dablock-visibility-index --url 'https://dablock.ai/mcp' --transport streamable-http
mcp_servers:
ai-dablock-visibility-index:
url: "https://dablock.ai/mcp" {
"McpServers": {
"ai-dablock-visibility-index": {
"Transport": "http",
"Url": "https://dablock.ai/mcp"
}
}
} assistant mcp add ai-dablock-visibility-index -t streamable-http -u 'https://dablock.ai/mcp'
{
"mcpServers": {
"ai-dablock-visibility-index": {
"type": "http",
"url": "https://dablock.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 +1
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://dablock.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dablock.ai | CN=WE1,O=Google Trust Services,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c4f7fee9d1acd97a0e8cb7fdcfcd4467 |
| SANs: dablock.ai, *.dablock.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dablock.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| dablock.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dablock.ai/mcp | Verified | 200 | |
| http (plaintext) | http://dablock.ai/mcp | HTTPS enforced | 301 | https://dablock.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_brand_visibility Look up one brand ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Brand slug, lowercase with hyphens — 'slack', 'coinbase', 'monday-com'. Not the display name. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name as published. |
| commercial_intent | number | – | How commercially loaded the brand's category demand is. |
| engines | array | – | Engines measured in this release. |
| is_client | boolean | – | Whether the brand is a client of the publisher. Placement cannot be bought; this flag makes that checkable. |
| measured_at | string | yes | Date of this release, ISO 8601. |
| niche_title | string | – | – |
| panel_version | integer | – | Prompt panel version. Figures from different versions are not comparable. |
| per_engine | object | – | Share of answer per engine, same scale. |
| prompts | array | – | Panel prompts in which the brand is named. |
| quadrant | string | – | Position on visibility against commercial intent. |
| rank | integer | yes | Position in this release, 1 = most named. |
| slug | string | yes | Identifier used by get_brand_visibility. |
| visibility_score | number | yes | Share of answer, percent of panel prompts naming the brand. |
No examples provided.
get_history Full measurement time series ~258
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| measurements | array | – | – |
| series | object | – | Per brand slug, the share of answer at each release. |
No examples provided.
get_methodology How the index is measured ~233
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | – | Engines measured in this release. |
| license | string | – | – |
| measured_at | string | – | Date of this release, ISO 8601. |
| niche_title | string | – | – |
| panel_version | integer | – | Prompt panel version. Figures from different versions are not comparable. |
| prompt_panel | array | – | The exact prompts, verbatim. |
| publisher | string | – | – |
| resolution | string | – | Percentage points one mention on one engine is worth. |
| scoring | string | – | How share of answer is computed. |
No examples provided.
get_visibility_index DABLOCK AI Visibility Index — full table ~240
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | – | Engines measured in this release. |
| entries | array | yes | – |
| measured_at | string | yes | Date of this release, ISO 8601. |
| niche_title | string | – | – |
| panel_version | integer | – | Prompt panel version. Figures from different versions are not comparable. |
No examples provided.
list_tracked_brands List tracked brands and slugs ~191
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| brands | array | yes | – |
No examples provided.
What is the DABLOCK AI Visibility Index MCP server?
DABLOCK AI Visibility Index is an MCP server listed in the public MCP registry as ai.dablock/visibility-index. Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site. This page covers its hosted endpoint (https://dablock.ai/mcp).
Is the DABLOCK AI Visibility Index MCP server safe to use?
DABLOCK AI Visibility Index scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DABLOCK AI Visibility Index MCP server expose?
DABLOCK AI Visibility Index exposes 5 tools: get_visibility_index, get_brand_visibility, list_tracked_brands, get_history, get_methodology. Their descriptions and schemas cost roughly 1,161 tokens of context every time the server is loaded.
Does the DABLOCK AI Visibility Index MCP server require authentication?
No. We connected to DABLOCK AI Visibility Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DABLOCK AI Visibility Index MCP server still maintained?
DABLOCK AI Visibility Index is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.