# Jhtdb (npm · @pipeworx/mcp-jhtdb)

Johns Hopkins Turbulence Databases (JHTDB) — point queries on reference direct numerical…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-jhtdb/jhtdb-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-jhtdb/jhtdb-mcp)
- npm · `@pipeworx/mcp-jhtdb`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb.md), [page](https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-jhtdb`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jhtdb).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-jhtdb -- npx -y @pipeworx/mcp-jhtdb
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-jhtdb": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jhtdb"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-jhtdb": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jhtdb"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-jhtdb -- npx -y @pipeworx/mcp-jhtdb
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-jhtdb": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-jhtdb"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-jhtdb --command npx --arg -y --arg @pipeworx/mcp-jhtdb
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-jhtdb:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-jhtdb"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-jhtdb": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-jhtdb"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-jhtdb -t stdio -c npx -a -y @pipeworx/mcp-jhtdb
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-jhtdb": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jhtdb"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 65, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `jhtdb_datasets` (~115 tokens)

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.

### `jhtdb_point_query` (~283 tokens)

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.

Input parameters:

- `dataset` (string, required): Dataset code from jhtdb_datasets, e.g. "isotropic1024coarse".
- `field` (string): Physical quantity to query. Default "velocity".
- `points` (array, required): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 65
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Jhtdb MCP server?

VerifyMCP ran 16 checks on Jhtdb, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-jhtdb
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-jhtdb
- Repository: https://github.com/pipeworx-io/mcp-jhtdb
- Website: https://pipeworx.io/packs/jhtdb
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-jhtdb/pipeworx-mcp-jhtdb