Remote MCP · Endpoint

Turbulence Modeling Resource MCP server

No. Turbulence Modeling Resource answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/turbulence-modeling-resource/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/turbulence-modeling-resource
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
NASA Langley Turbulence Modeling Resource (TMR) — verification and validation cases for…
Listing
From the official MCP registry (active).
Recent checks of Turbulence Modeling Resource
CheckedResultHandshake
42 minutes agoHandshake completed55 ms
9 days agoHandshake completed111 ms
10 days agoHandshake completed1.52 s
11 days agoHandshake completed261 ms
12 days agoHandshake completed162 ms
14 days agoHandshake completed127 ms
14 days agoHandshake completed157 ms
15 days agoHandshake completed108 ms
17 days agoHandshake completed165 ms
19 days agoHandshake completed77 ms
21 days agoHandshake completed838 ms
24 days agoHandshake completed98 ms
26 days agoHandshake completed52 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 Turbulence Modeling Resource and makes no claim about it beyond what these checks measured.