Jhtdb
NPM · @PIPEWORX/MCP-JHTDB · 2 COMPONENTS
Johns Hopkins Turbulence Databases (JHTDB) — point queries on reference direct numerical…
Available components
Last scanned (5 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jhtdb). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 452 tokens (~226/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-jhtdb@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-jhtdb |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-jhtdb/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649459916 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ff2bcb11b3c74cccbbded0c81b11fa9155455b01b328df3ff1f1f91df3c20d88e18cab12599d791374c53d1ce02deb0506166cc54aa469c2c156c9c00 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jhtdb_datasets ~115
Catalog of Johns Hopkins Turbulence Databases (JHTDB) datasets available for point queries — forced isotropic turbulence, channel flow, MHD turbulence, transitional boundary layer, atmospheric boundary layer and wind-farm LES, and more. Each entry gives the dataset code to pass to jhtdb_point_query, its spatial domain (x/y/z ranges, in the dataset's native simulation units), grid resolution, time range, and which physical fields (velocity, pressure, magnetic field, temperature, ...) it carries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jhtdb_point_query ~283
Interpolated velocity, pressure, or velocity-gradient values at up to 10 points and a single time in a Johns Hopkins Turbulence Databases (JHTDB) reference DNS/LES dataset. Values are returned in the dataset's native simulation units (dimensionless DNS code units for the isotropic/channel/MHD datasets; physical meters/seconds for the atmospheric-boundary-layer and wind-farm LES datasets) — call jhtdb_datasets first to see a dataset's domain and time range. Uses JHTDB's public testing authorization token, capped well under its documented small-query allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Dataset code from jhtdb_datasets, e.g. "isotropic1024coarse". |
| field | string | – | Physical quantity to query. Default "velocity". |
| points | array | yes | 1 to 10 points, each {x, y, z} in the dataset's native spatial units. |
| spatial_interpolation | string | – | Spatial interpolation kernel. Defaults to Lag4 for velocity/pressure, None_Fd4 (4th-order finite difference, no interpolation) for velocity_gradient. |
| temporal_interpolation | string | – | Temporal interpolation. Default "None". |
| time | number | – | Simulation time at which to evaluate the field, within the dataset's time range from jhtdb_datasets. |
No output schema declared.
No examples provided.
How do I install the Jhtdb MCP server?
Jhtdb runs locally as an npm package, launched with npx -y @pipeworx/mcp-jhtdb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-jhtdb
claude mcp add pipeworx-io-jhtdb -- npx -y @pipeworx/mcp-jhtdb
What is the Jhtdb MCP server?
Jhtdb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jhtdb. Johns Hopkins Turbulence Databases (JHTDB), point queries on reference direct numerical… This page covers its npm package (@pipeworx/mcp-jhtdb).
Is the Jhtdb MCP server safe to use?
Jhtdb scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jhtdb MCP server expose?
Jhtdb exposes 2 tools: jhtdb_datasets, jhtdb_point_query. Their descriptions and schemas cost roughly 398 tokens of context every time the server is loaded.
Is the Jhtdb MCP server still maintained?
Jhtdb is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Jhtdb MCP server under?
Jhtdb declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.