# NI-DAQmx DAQ Devices (pypi · labmcp-ni-daqmx)

MCP server for National Instruments DAQ devices (NI-DAQmx).

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- pypi · `labmcp-ni-daqmx`: 82/100 (this document), [markdown](https://verifymcp.io/servers/k-dense-ai-labmcp-ni-daqmx/labmcp-ni-daqmx.md), [page](https://verifymcp.io/servers/k-dense-ai-labmcp-ni-daqmx/labmcp-ni-daqmx)

## Channel facts

- Registry: `pypi`
- Package: `labmcp-ni-daqmx`
- Version: `0.1.2`
- 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-09-30.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 5 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1735 tokens (~157/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the NI-DAQmx DAQ Devices MCP server?

NI-DAQmx DAQ Devices runs locally as a PyPI package, launched with uvx labmcp-ni-daqmx. 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 k-dense-ai-labmcp-ni-daqmx -- uvx labmcp-ni-daqmx
```

### Cursor

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-ni-daqmx": {
      "command": "uvx",
      "args": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k-dense-ai-labmcp-ni-daqmx": {
      "command": "uvx",
      "args": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k-dense-ai-labmcp-ni-daqmx -- uvx labmcp-ni-daqmx
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-ni-daqmx": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-ni-daqmx"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k-dense-ai-labmcp-ni-daqmx --command uvx --arg labmcp-ni-daqmx
```

### Hermes

```yaml
mcp_servers:
  k-dense-ai-labmcp-ni-daqmx:
    command: "uvx"
    args: ["labmcp-ni-daqmx"]
```

### Netclaw

```json
{
  "McpServers": {
    "k-dense-ai-labmcp-ni-daqmx": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k-dense-ai-labmcp-ni-daqmx -t stdio -c uvx -a labmcp-ni-daqmx
```

### Other

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-ni-daqmx": {
      "command": "uvx",
      "args": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}
```

## 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-09-30 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-29 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-28 (score 81, +42)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 39, −31)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-09-26 (score 70)

First indexed and scored.

## MCP tools (11)

### `get_connection_info` (~40 tokens)

Get Connection Info

Report which instrument is connected (identity, address, simulated or real),
whether the server is read-only, and the active safety limits. Call this first.

### `get_command_log` (~46 tokens)

Get Command Log

Return the most recent raw commands sent to / replies received from the
instrument (newest last). Useful for debugging and for recording what was done.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (array)

### `reconnect` (~35 tokens)

Reconnect

Close and re-open the connection to the instrument (e.g. after it was power
cycled or a cable was re-plugged).

### `list_devices` (~46 tokens)

List Devices

List every NI-DAQmx device the driver can see (product type, serial number, channels,
whether it is an NI MAX simulated device) and which one this server is connected to.

Output parameters:

- `connected_device` (string)
- `devices` (array)
- `nidaqmx_driver_version` (string)
- `timestamp` (string)

### `get_device_info` (~52 tokens)

Get Device Info

Describe the connected device: analog input/output channels, digital lines, supported
voltage ranges, maximum sample rates, and the outputs this server has set. Call this before
choosing channels, ranges and rates.

Output parameters:

- `ai_max_multi_channel_rate_hz`: Aggregate rate over all channels (multiplexed devices)
- `ai_max_single_channel_rate_hz`
- `ai_simultaneous_sampling`
- `ai_voltage_ranges_v` (array): Supported [min, max] input ranges
- `analog_inputs` (array)
- `analog_outputs` (array)
- `ao_last_written_v` (object): Values this server wrote to AO channels
- `ao_voltage_ranges_v` (array): Supported [min, max] output ranges
- `di_lines` (array)
- `digital_lines` (array)
- `do_last_written` (object): Levels this server wrote to DO lines (true = high)
- `do_lines` (array)
- `is_simulated` (boolean): True for an NI MAX simulated device
- `name` (string)
- `product_category`
- `product_type`
- `serial_number`: Hexadecimal, as shown in NI MAX
- `timestamp` (string)

### `read_analog` (~287 tokens)

Read Analog

Measure voltage on one or more analog inputs: a single on-demand reading, or a finite
hardware-timed acquisition of `samples` per channel at `rate_hz`. Returns per-channel
statistics and a downsampled waveform; optionally saves all data to CSV.

Bounded by the `max_samples`, `max_rate_hz` and `max_acquisition_s` limits; the device's own
maximum rate (shared by all channels on multiplexed devices) also applies. Blocks for
samples / rate_hz seconds.

Input parameters:

- `channels` (string, required): Analog inputs, e.g. 'ai0', 'ai0:3' or 'Dev1/ai0, Dev1/ai4'
- `max_points` (integer): Max points per channel in the returned waveform
- `max_v` (number): Highest expected voltage (sets the input range)
- `min_v` (number): Lowest expected voltage (sets the input range)
- `rate_hz`: Sample clock rate per channel (required if samples > 1)
- `samples` (integer): Samples per channel; 1 = one on-demand reading
- `save_path`: Write all samples to this new .csv file (never overwritten)
- `terminal_config` (string): Input wiring: rse = single-ended to AI GND, diff = differential, nrse = to AI SENSE

Output parameters:

- `channels` (array)
- `downsample_factor` (integer): Samples per min/max pair (1 = every sample returned)
- `sample_rate_hz`: Actual sample clock rate (None for one on-demand sample)
- `samples_per_channel` (integer)
- `saved_to`
- `stats` (array)
- `time_s` (array): Time of each returned point from the first sample
- `timestamp` (string)
- `unit` (string)
- `warnings` (array): NI-DAQmx warnings raised during the acquisition
- `waveforms` (object): Data per channel (all data if small). Downsampled data keeps each block's minimum and maximum in time order (placed at the block's first and last sample time), so spikes are not lost

### `read_thermocouple` (~330 tokens)

Read Thermocouple

Measure temperature (°C) with thermocouples (types B, E, J, K, N, R, S, T) on a
thermocouple-capable device, e.g. an NI 9211/9212/9213/9214 module or USB-TC01.

Use cjc_source='built_in' on modules with a cold-junction sensor; 'constant' uses cjc_value_c
(accuracy then depends on how well you know the terminal temperature). Devices without
thermocouple support return an NI-DAQmx error.

Input parameters:

- `channels` (string, required): Thermocouple inputs, e.g. 'ai0' or 'ai0:3' (on a thermocouple-capable device/module)
- `cjc_source` (string): 'built_in' = the module's cold-junction sensor (e.g. NI 9211/9213, USB-TC01); 'constant' = cjc_value_c
- `cjc_value_c` (number): Cold-junction temperature in °C when cjc_source='constant'
- `max_c` (number): Highest expected temperature, °C
- `max_points` (integer)
- `min_c` (number): Lowest expected temperature, °C
- `rate_hz`: Sample rate if samples > 1
- `samples` (integer): Samples per channel; 1 = one reading
- `save_path`: Write all samples to this new .csv file (never overwritten)
- `thermocouple_type` (string)

Output parameters:

- `channels` (array)
- `downsample_factor` (integer): Samples per min/max pair (1 = every sample returned)
- `sample_rate_hz`: Actual sample clock rate (None for one on-demand sample)
- `samples_per_channel` (integer)
- `saved_to`
- `stats` (array)
- `time_s` (array): Time of each returned point from the first sample
- `timestamp` (string)
- `unit` (string)
- `warnings` (array): NI-DAQmx warnings raised during the acquisition
- `waveforms` (object): Data per channel (all data if small). Downsampled data keeps each block's minimum and maximum in time order (placed at the block's first and last sample time), so spikes are not lost

### `read_digital_lines` (~105 tokens)

Read Digital Lines

Read the logic level of digital lines.

Lines that this server is driving as outputs are reported from their last commanded level and
are NOT re-read: an NI-DAQmx digital-input task would switch them to inputs and release
whatever they drive. Reading a line another program drives may likewise make it an input.

Input parameters:

- `lines` (string, required): Digital lines, e.g. 'port0/line0:3' or 'Dev1/port1/line0'

Output parameters:

- `lines` (array)
- `timestamp` (string)

### `write_analog` (~150 tokens)

Write Analog

Set an analog output to a DC voltage (static, software-timed). The output keeps this value
after the call on most NI devices, until changed or `set_outputs_safe` is called.

This energises whatever the output drives (valve or heater controllers, laser drivers,
actuators). Checked against `max_ao_voltage_v` (absolute value) and the device's AO range
(e.g. USB-6008/6009: 0-5 V) before anything is sent.

Input parameters:

- `channel` (string, required): One analog output, e.g. 'ao0' or 'Dev1/ao1'
- `voltage_v` (number, required): DC output voltage in V

Output parameters:

- `channel` (string)
- `timestamp` (string)
- `voltage_v` (number)

### `write_digital_lines` (~132 tokens)

Write Digital Lines

Drive digital output lines high or low. The lines keep their level after the call until
changed or `set_outputs_safe` is called.

Digital outputs often switch relays, valves, pumps or trigger other instruments; confirm with
the user what each line controls. Voltage levels depend on the device (e.g. 5 V TTL or 3.3 V).

Input parameters:

- `levels` (array, required): One level for all lines, or one per line in order
- `lines` (string, required): Digital lines, e.g. 'port0/line0' or 'port0/line0:3'

Output parameters:

- `lines` (array)
- `timestamp` (string)

### `set_outputs_safe` (~102 tokens)

Set Outputs Safe

Put the device's outputs in a safe state: every analog output to 0 V (or the bottom of its
range if 0 V is not in it) and, by default, every digital line this server drove - plus the
\`safe_do_lines` option lines - driven low. Use when finished or if anything looks wrong.

Input parameters:

- `digital_low` (boolean): Also drive low every DO line this server drove (and the safe_do_lines option)

Output parameters:

- `actions` (array)
- `timestamp` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k-dense-ai-labmcp-ni-daqmx/labmcp-ni-daqmx#diagnostics

## Score history

- 2026-09-30: 82
- 2026-09-29: 66
- 2026-09-28: 81
- 2026-09-27: 39
- 2026-09-26: 70

## Common questions

### What is the NI-DAQmx DAQ Devices MCP server?

NI-DAQmx DAQ Devices is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-ni-daqmx. MCP server for National Instruments DAQ devices (NI-DAQmx). This page covers its PyPI package (labmcp-ni-daqmx).

### Is the NI-DAQmx DAQ Devices MCP server safe to use?

NI-DAQmx DAQ Devices scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 2026. 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 NI-DAQmx DAQ Devices MCP server expose?

NI-DAQmx DAQ Devices exposes 11 tools: get_connection_info, get_command_log, reconnect, list_devices, get_device_info, and 6 more. Their descriptions and schemas cost roughly 1,325 tokens of context every time the server is loaded.

### Is the NI-DAQmx DAQ Devices MCP server still maintained?

NI-DAQmx DAQ Devices is still listed as active in the MCP registry. We last reached this channel on 30 September 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 NI-DAQmx DAQ Devices MCP server under?

NI-DAQmx DAQ Devices declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/labmcp-ni-daqmx/
- Socket report: https://socket.dev/pypi/package/labmcp-ni-daqmx
- Repository: https://github.com/K-Dense-AI/lab-instrument-mcps
- Website: https://github.com/K-Dense-AI/lab-instrument-mcps/tree/main/servers/engineering/ni-daqmx
- Changelog RSS feed: https://verifymcp.io/servers/k-dense-ai-labmcp-ni-daqmx/labmcp-ni-daqmx.xml
- Changelog JSON feed: https://verifymcp.io/servers/k-dense-ai-labmcp-ni-daqmx/labmcp-ni-daqmx.json
- HTML version of this page: https://verifymcp.io/servers/k-dense-ai-labmcp-ni-daqmx/labmcp-ni-daqmx