Remote MCP · Endpoint

Gradient Dynamics: thermal and CFD simulation MCP server

Yes, as of 9 hours ago: the request timed out.

DownLast checked 9 hours ago

Server URL

https://api.gradient-dynamics.com/mcp

The last check failed: the request timed out.

Registry name
com.gradient-dynamics/engineering
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
86 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
GPU CFD and conjugate heat transfer for cold plates, heat sinks, battery packs and electronics.
Listing
From the official MCP registry (active).
Recent checks of Gradient Dynamics: thermal and CFD simulation
CheckedResultHandshake
9 hours agoFailed - the request timed out—
4 days agoHandshake completed310 ms
7 days agoHandshake completed323 ms

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

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 Gradient Dynamics: thermal and CFD simulation and makes no claim about it beyond what these checks measured.