Remote MCP · Endpoint

Jhtdb MCP server

No. Jhtdb answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/jhtdb/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/jhtdb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Johns Hopkins Turbulence Databases (JHTDB) — point queries on reference direct numerical…
Listing
From the official MCP registry (active).
Recent checks of Jhtdb
CheckedResultHandshake
42 minutes agoHandshake completed66 ms
9 days agoHandshake completed105 ms
10 days agoHandshake completed157 ms
11 days agoHandshake completed93 ms
12 days agoHandshake completed1.23 s
14 days agoHandshake completed199 ms
14 days agoHandshake completed747 ms
15 days agoHandshake completed101 ms
17 days agoHandshake completed151 ms
19 days agoHandshake completed63 ms
22 days agoHandshake completed90 ms
24 days agoHandshake completed85 ms
26 days agoHandshake completed995 ms

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

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