Remote MCP · Endpoint

DatoQA MCP server

No. DatoQA answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://datoqa.bhazarstudio.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.bhazarstudio.datoqa/datoqa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
666 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Sourced data and FX across 30 currencies; table validation, paid reconciliation and file conversion.
Listing
From the official MCP registry (active).
Recent checks of DatoQA
CheckedResultHandshake
1 day agoHandshake completed666 ms
3 days agoHandshake completed602 ms
5 days agoHandshake completed548 ms
7 days agoHandshake completed345 ms
9 days agoHandshake completed915 ms
11 days agoHandshake completed119 ms
12 days agoHandshake completed350 ms
13 days agoHandshake completed729 ms
15 days agoHandshake completed282 ms
17 days agoHandshake completed368 ms
19 days agoHandshake completed276 ms
20 days agoHandshake completed328 ms
22 days agoHandshake completed335 ms
23 days agoHandshake completed203 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with DatoQA and makes no claim about it beyond what these checks measured.