Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DatoQA — Official Public Holidays

REMOTE · DATOQA.BHAZARSTUDIO.WORKERS.DEV

Government and OpenHolidays calendars: regional scope, multilingual names, dated sources and gaps.

0 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security69
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 867 tokens (~173/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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 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.

  • 8 Oct 26 0
    • Tool coverage: 73% → 100% ▲ functional
  • 4 Oct 26 0
    • Server version: 0.6.12 → 0.6.14 functional
  • 2 Oct 26 0
    • Server version: 0.6.10 → 0.6.12 functional
Diagnostics

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 21 Nov 2026 · Probed https://datoqa.bhazarstudio.workers.dev/mcp/holidays

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bhazarstudio.workers.dev CN=YE1,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA384 5b4890481c6d3517477e644a8103648c9cb
SANs: *.bhazarstudio.workers.dev, bhazarstudio.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of datoqa.bhazarstudio.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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=15552000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://datoqa.bhazarstudio.workers.dev/mcp/holidays Verified 200
http (plaintext) http://datoqa.bhazarstudio.workers.dev/mcp/holidays Served over HTTP 200
MCP tools · 5 exposed · ~750 tokens

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 →

Tool Tokens
catalog ~311

Inspect this connection’s scope, tools and access policy. With no arguments returns the usual catalog. On the general or economy connection, optionally supply report_countries (1–10 World Bank codes) for a FREE live preview of the optional paid country comparison: population/GDP/inflation by default, or up to six selected historical indicators over ten years, aligned JSON and CSV, definitions and source evidence. Preview reports price, missing cells, availability and the exact HTTP purchase path; it never signs or pays. Existing data tools remain free. Buying requires an authorized x402 HTTP client, not just MCP. Source/schema checks are not independent factual verification.

NameTypeReqDescription
languagestring–Response metadata language, English by default or French; original source definitions and notes remain preserved.
report_countriesarray–Optional free preview for these distinct World Bank country codes, e.g. FRA, DEU, ESP. General/economy connections only.
report_frominteger–Inclusive first observation year for a custom country preview. Supply with report_to and report_indicators; at most ten years, from 1960 onward.
report_indicatorsarray–Custom historical comparison: select up to six of the 22 WDI indicators. Supply report_from and report_to together, up to ten years. Missing cells block payment.
report_tointeger–Inclusive last observation year, no later than the last completed calendar year. Supply with report_from and report_indicators; missing observations block purchase.
NameTypeReqDescription
available_recordsinteger––
capabilitiesarray––
independently_verifiedboolean–Official-source checks are not independent factual corroboration.
namestringyes–
profilestring––
titlestring––
toolsarray––
versionstring––

No examples provided.

get_evidence ~61

Retrieve the source JSON snapshot and SHA-256 digest for a currently available record. The digest proves snapshot integrity, not factual truth.

NameTypeReqDescription
idstringyesRecord id returned by a DatoQA data response; returns the retained source snapshot for that record.
NameTypeReqDescription
first_observed_atstringyes–
hash_scopestringyes–
noticestringyes–
record_idstringyes–
sha256stringyes–
source_payload_jsonstringyes–
source_urlstringyes–

No examples provided.

get_public_holidays ~240

Get published public-holiday entries for one calendar and year or exact inclusive local date. Use a known region id directly (fr-metropole, gb-england-and-wales, hk-general, oh-de); consult list_holiday_regions only if scope is unknown. OpenHolidays entries retain multilingual names, subdivisions and half-day scope; set nationwide_only=true to exclude regional entries. Government feeds and third-party curated calendars are explicitly distinguished. Empty results do not establish working days; future dates can change, and aggregator dates are not individually government-confirmed.

NameTypeReqDescription
datestring–Exact local calendar date YYYY-MM-DD, for example 2026-12-28; cannot be combined with year.
nationwide_onlyboolean–For OpenHolidays country calendars, keep only entries marked nationwide by the source. Default false includes regional entries with their scopes. Government calendars retain their named territory sco…
regionstringyesCalendar identifier from list_holiday_regions, for example gb-england-and-wales.
yearinteger–Calendar year; defaults to the current year. Only published years are available. Omit when date is supplied.
NameTypeReqDescription
available_yearsarray––
directorystring––
independently_verifiedboolean–Official-source checks are not independent factual corroboration.
itemsarrayyes–
noticestring––
regionstring––
requested_datestring|null––
returnedintegeryesDomain-specific result count, not necessarily the number of stored records in items.
statusstringyesRead this before using values; a successful transport does not establish data availability.
yearinteger––

No examples provided.

get_record ~60

Get an unexpired record with provenance and its explicit verification level. Source/schema validation is not independent factual verification.

NameTypeReqDescription
idstringyesOpaque record id returned by a DatoQA data response. Reuse it exactly; do not invent an id.
NameTypeReqDescription
citationobjectyes–
dataobjectyesSource-specific payload; inspect units, observation dates, nulls and source notes.
display_labelstring––
domainstringyes–
freshnessobjectyes–
idstringyes–
provenanceobjectyes–

No examples provided.

list_holiday_regions ~78

Discover available public-holiday calendars and exact region ids, published years, source kind and freshness. Includes FR/UK/HK government feeds and international OpenHolidays curated entries. Use when country/region/year coverage is unknown; otherwise call get_public_holidays directly. Configured calendars are not proof of available data. International coverage is incomplete.

Input schema present but exposes no named parameters.

NameTypeReqDescription
configured_regionsarrayyes–
count_meaningstringyes–
endpointstringyes–
independently_verifiedbooleanyesOfficial-source checks are not independent factual corroboration.
max_collection_age_secondsintegeryes–
noticestringyes–
refresh_interval_secondsintegeryes–
region_countintegeryes–
regionsarrayyes–
source_event_countintegeryes–

No examples provided.

Install

How do I install the DatoQA — Official Public Holidays MCP server?

DatoQA — Official Public Holidays is a hosted endpoint at https://datoqa.bhazarstudio.workers.dev/mcp/holidays, 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 · datoqa.bhazarstudio.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-bhazarstudio-datoqa-official-public- 'https://datoqa.bhazarstudio.workers.dev/mcp/holidays'
Common questions

What is the DatoQA — Official Public Holidays MCP server?

DatoQA — Official Public Holidays is an MCP server listed in the public MCP registry as dev.workers.bhazarstudio.datoqa/official-public-holidays. Government and OpenHolidays calendars: regional scope, multilingual names, dated sources and gaps. This page covers its hosted endpoint (https://datoqa.bhazarstudio.workers.dev/mcp/holidays).

Is the DatoQA — Official Public Holidays MCP server safe to use?

DatoQA — Official Public Holidays scores 83 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 DatoQA — Official Public Holidays MCP server expose?

DatoQA — Official Public Holidays exposes 5 tools: catalog, list_holiday_regions, get_public_holidays, get_record, get_evidence. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.

Does the DatoQA — Official Public Holidays MCP server require authentication?

No. We connected to DatoQA — Official Public Holidays without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DatoQA — Official Public Holidays MCP server still maintained?

DatoQA — Official Public Holidays is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the DatoQA — Official Public Holidays MCP server?

VerifyMCP ran 13 checks on DatoQA — Official Public Holidays, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.