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 — Historical Exchange Rates

REMOTE · DATOQA.BHAZARSTUDIO.WORKERS.DEV · SCANNED SEP 28

ECB EUR reference exchange rates since 1999, with exact dates and gaps. Not live trading prices.

71 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 598 tokens (~99/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the DatoQA — Historical Exchange Rates MCP server?

DatoQA — Historical Exchange Rates is a hosted endpoint at https://datoqa.bhazarstudio.workers.dev/mcp/fx, 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-historical-excha 'https://datoqa.bhazarstudio.workers.dev/mcp/fx'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-workers-bhazarstudio-datoqa-historical-excha": {
      "url": "https://datoqa.bhazarstudio.workers.dev/mcp/fx"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-workers-bhazarstudio-datoqa-historical-excha": {
      "type": "http",
      "url": "https://datoqa.bhazarstudio.workers.dev/mcp/fx"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-workers-bhazarstudio-datoqa-historical-excha]
url = "https://datoqa.bhazarstudio.workers.dev/mcp/fx"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-bhazarstudio-datoqa-historical-excha": {
      "type": "remote",
      "url": "https://datoqa.bhazarstudio.workers.dev/mcp/fx",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-workers-bhazarstudio-datoqa-historical-excha --url 'https://datoqa.bhazarstudio.workers.dev/mcp/fx' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-workers-bhazarstudio-datoqa-historical-excha:
    url: "https://datoqa.bhazarstudio.workers.dev/mcp/fx"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-workers-bhazarstudio-datoqa-historical-excha": {
      "Transport": "http",
      "Url": "https://datoqa.bhazarstudio.workers.dev/mcp/fx"
    }
  }
}
# add to Vellum
assistant mcp add dev-workers-bhazarstudio-datoqa-historical-excha -t streamable-http -u 'https://datoqa.bhazarstudio.workers.dev/mcp/fx'
// mcp.json
{
  "mcpServers": {
    "dev-workers-bhazarstudio-datoqa-historical-excha": {
      "type": "http",
      "url": "https://datoqa.bhazarstudio.workers.dev/mcp/fx"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 70

    First indexed and scored.

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 28 Sept 2026 · Probed https://datoqa.bhazarstudio.workers.dev/mcp/fx

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=YE2,O=Let's Encrypt,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA384 5ab0e87130a64d96f2f3d39cc4055a1aac7
SANs: *.bhazarstudio.workers.dev, bhazarstudio.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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. present 60074 8 Verified
workers.dev. 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=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/fx Verified 200
http (plaintext) http://datoqa.bhazarstudio.workers.dev/mcp/fx Inconclusive 406
MCP tools · 6 exposed · ~485 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 ~79

Get the scope, allowed tool names, source IDs, endpoint and access policy for this thematic MCP. Call with no arguments when setting up this connection; skip it when the desired data tool and inputs are known. Use the listed domain directories only to resolve missing identifiers or coverage. This static catalog does not guarantee current availability; inspect the data response status and freshness.

Input schema present but exposes no named parameters.

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_exchange_rate_history ~168

ECB historical daily reference rates for one currency against EUR. Provide year (1999 onward) or an exact date, not both. Default: current year. Returns one year at most, original decimals, missing values and evidence. No weekend carry-forward, interpolation, current quote for discontinued currencies, cross rates or executable prices.

NameTypeReqDescription
currencystringyesUppercase non-EUR currency code from list_exchange_rate_history, for example USD. Values are currency units per one EUR.
datestring–Exact source date YYYY-MM-DD, for example 2008-09-15; cannot be combined with year. No filling of weekends or gaps.
yearinteger–One source calendar year since 1999; defaults to the current year. Cannot be combined with date.
NameTypeReqDescription
currencystringyes–
directorystring––
independently_verifiedboolean–Official-source checks are not independent factual corroboration.
interpretationobject––
itemsarrayyes–
noticestring––
requested_datestring|nullyes–
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.
yearintegeryes–

No examples provided.

get_exchange_rates ~70

ECB indicative daily currency reference rates against EUR. Not real-time or executable prices; inspect observation_date. Original rates freely available at the cited ECB source.

NameTypeReqDescription
currencystring–Optional uppercase currency code, for example USD; omit for all available ECB reference currencies. Values are currency units per one EUR.
NameTypeReqDescription
available_currenciesarray––
directorystring––
independently_verifiedboolean–Official-source checks are not independent factual corroboration.
itemsarrayyes–
noticestring––
returnedintegeryesDomain-specific result count, not necessarily the number of stored records in items.
selected_rate–––
statusstringyesRead this before using values; a successful transport does not establish data availability.

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_exchange_rate_history ~47

List available currencies, annual snapshots since 1999 and explicit gaps in ECB daily reference FX history. Some currencies have been discontinued. Units per EUR; original data freely available at ECB.

Input schema present but exposes no named parameters.

NameTypeReqDescription
base_currencystringyes–
currenciesarrayyes–
endpointstringyes–
frequencystringyes–
independently_verifiedbooleanyesOfficial-source checks are not independent factual corroboration.
missing_or_expired_yearsarrayyes–
numeric_valuesintegeryes–
original_data_freebooleanyes–
querystringyes–
refreshstringyes–
sourcestringyes–
yearsarrayyes–

No examples provided.

Common questions

What is the DatoQA — Historical Exchange Rates MCP server?

DatoQA — Historical Exchange Rates is an MCP server listed in the public MCP registry as dev.workers.bhazarstudio.datoqa/historical-exchange-rates. ECB EUR reference exchange rates since 1999, with exact dates and gaps. Not live trading prices. This page covers its hosted endpoint (https://datoqa.bhazarstudio.workers.dev/mcp/fx).

Is the DatoQA — Historical Exchange Rates MCP server safe to use?

DatoQA — Historical Exchange Rates scores 71 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 — Historical Exchange Rates MCP server expose?

DatoQA — Historical Exchange Rates exposes 6 tools: catalog, get_exchange_rates, list_exchange_rate_history, get_exchange_rate_history, get_record, get_evidence. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.

Does the DatoQA — Historical Exchange Rates MCP server require authentication?

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

Is the DatoQA — Historical Exchange Rates MCP server still maintained?

DatoQA — Historical Exchange Rates is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.