Remote MCP · Endpoint

TidyData Tools MCP server

No. TidyData Tools answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://tidydata-api.tidydata.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.tidydata-dev/tidydata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
520 ms
Tools exposed
51 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Holidays, business days, currency, time zones, DNS/WHOIS, web page checks, geodata and text tools.
Listing
From the official MCP registry (active).
Recent checks of TidyData Tools
CheckedResultHandshake
2 days agoHandshake completed520 ms
3 days agoHandshake completed629 ms
3 days agoHandshake completed588 ms
5 days agoHandshake completed497 ms
6 days agoHandshake completed527 ms
7 days agoHandshake completed484 ms
8 days agoHandshake completed450 ms
9 days agoHandshake completed505 ms
11 days agoHandshake completed1.23 s
13 days agoHandshake completed486 ms
16 days agoHandshake completed739 ms
18 days agoHandshake completed466 ms
21 days agoHandshake completed482 ms
22 days agoHandshake completed567 ms
25 days agoHandshake completed974 ms

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

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 TidyData Tools and makes no claim about it beyond what these checks measured.