Home / MCP registry index / com.gradient-dynamics/engineering

Gradient Dynamics: thermal and CFD simulation

com.gradient-dynamics/engineering in the official MCP registry. Endpoint https://api.gradient-dynamics.com/mcp.

The registry describes it as: GPU CFD and conjugate heat transfer for cold plates, heat sinks, battery packs and electronics.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http engineering https://api.gradient-dynamics.com/mcp

{
  "mcpServers": {
    "engineering": {
      "url": "https://api.gradient-dynamics.com/mcp"
    }
  }
}

code --add-mcp '{"name":"engineering","type":"http","url":"https://api.gradient-dynamics.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_tools get_tool_schema get_capabilities list_projects create_project import_surface_attachment create_upload open_surface_upload prepare_surface_upload complete_surface_upload view_geometry inspect_mesh_geometry check_geometry plan_mesh validate_mesh create_mesh get_mesh_controls validate_simulation run_simulation get_solver_controls estimate_cost get_job list_jobs list_activity get_job_events get_operation cancel_job review_job prepare_job_viewer view_mesh view_mesh_section view_simulation_result list_artifacts get_artifact read_artifact_summary get_artifact_download list_templates get_template create_geometry create_design_preview get_design_preview prepare_surface_heatmap list_design_drafts get_design_draft publish_design_batch finish_design_draft get_design_checkpoint reconstruct_cad edit_reconstructed_cad get_cad_reconstruction get_design_operation_schema call_design_operation prepare_cold_plate_simulation import_design_source_attachment open_design_source_upload prepare_design_source_upload complete_design_source_upload read_design_source create_design_brief get_design_brief and 26 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-13): 416ff66dd2371e13. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-gradient-dynamics-engineering/badge.svg)](https://lazaretto.dev/mcp-registry/com-gradient-dynamics-engineering)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.