NI-DAQmx DAQ Devices
PYPI · LABMCP-NI-DAQMX · SCANNED SEP 30
MCP server for National Instruments DAQ devices (NI-DAQmx).
Available components
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 5 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
pypi · labmcp-ni-daqmx
claude mcp add k-dense-ai-labmcp-ni-daqmx -- uvx labmcp-ni-daqmx
{
"mcpServers": {
"k-dense-ai-labmcp-ni-daqmx": {
"command": "uvx",
"args": [
"labmcp-ni-daqmx"
]
}
}
} {
"servers": {
"k-dense-ai-labmcp-ni-daqmx": {
"command": "uvx",
"args": [
"labmcp-ni-daqmx"
]
}
}
} codex mcp add k-dense-ai-labmcp-ni-daqmx -- uvx labmcp-ni-daqmx
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"k-dense-ai-labmcp-ni-daqmx": {
"type": "local",
"command": [
"uvx",
"labmcp-ni-daqmx"
],
"enabled": true
}
}
} openclaw mcp add k-dense-ai-labmcp-ni-daqmx --command uvx --arg labmcp-ni-daqmx
mcp_servers:
k-dense-ai-labmcp-ni-daqmx:
command: "uvx"
args: ["labmcp-ni-daqmx"] {
"McpServers": {
"k-dense-ai-labmcp-ni-daqmx": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"labmcp-ni-daqmx"
]
}
}
} assistant mcp add k-dense-ai-labmcp-ni-daqmx -t stdio -c uvx -a labmcp-ni-daqmx
{
"mcpServers": {
"k-dense-ai-labmcp-ni-daqmx": {
"command": "uvx",
"args": [
"labmcp-ni-daqmx"
]
}
}
} 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.
- 30 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Sept 26 +42
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −31
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 26 Sept 26 70
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 30 Sept 2026 · Analysed pypi/labmcp-ni-daqmx@0.1.2
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | K-Dense-AI/lab-instrument-mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/K-Dense-AI/lab-instrument-mcps/.github/workflows/release.yml@refs/tags/labmcp-ni-daqmx-v0.1.2 |
| Rekor log index | 2969517920 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:7318ab84ffc6a117ab93fe744c8bbd27a1e083cf1e79b9dbf1f972f980ebf5ea |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Stale | 5 |
| 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 →
get_command_log Get Command Log ~46
Return the most recent raw commands sent to / replies received from the instrument (newest last). Useful for debugging and for recording what was done.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_connection_info Get Connection Info ~40
Report which instrument is connected (identity, address, simulated or real), whether the server is read-only, and the active safety limits. Call this first.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_device_info Get Device Info ~52
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_max_multi_channel_rate_hz | – | yes | Aggregate rate over all channels (multiplexed devices) |
| ai_max_single_channel_rate_hz | – | yes | – |
| ai_simultaneous_sampling | – | yes | – |
| ai_voltage_ranges_v | array | yes | Supported [min, max] input ranges |
| analog_inputs | array | yes | – |
| analog_outputs | array | yes | – |
| ao_last_written_v | object | yes | Values this server wrote to AO channels |
| ao_voltage_ranges_v | array | yes | Supported [min, max] output ranges |
| di_lines | array | yes | – |
| digital_lines | array | yes | – |
| do_last_written | object | yes | Levels this server wrote to DO lines (true = high) |
| do_lines | array | yes | – |
| is_simulated | boolean | yes | True for an NI MAX simulated device |
| name | string | yes | – |
| product_category | – | yes | – |
| product_type | – | yes | – |
| serial_number | – | yes | Hexadecimal, as shown in NI MAX |
| timestamp | string | yes | – |
No examples provided.
list_devices List Devices ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| connected_device | string | yes | – |
| devices | array | yes | – |
| nidaqmx_driver_version | string | yes | – |
| timestamp | string | yes | – |
No examples provided.
read_analog Read Analog ~287
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | string | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| downsample_factor | integer | yes | Samples per min/max pair (1 = every sample returned) |
| sample_rate_hz | – | yes | Actual sample clock rate (None for one on-demand sample) |
| samples_per_channel | integer | yes | – |
| saved_to | – | yes | – |
| stats | array | yes | – |
| time_s | array | yes | Time of each returned point from the first sample |
| timestamp | string | yes | – |
| unit | string | yes | – |
| warnings | array | yes | NI-DAQmx warnings raised during the acquisition |
| waveforms | object | yes | 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 |
No examples provided.
read_digital_lines Read Digital Lines ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lines | string | yes | Digital lines, e.g. 'port0/line0:3' or 'Dev1/port1/line0' |
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | yes | – |
| timestamp | string | yes | – |
No examples provided.
read_thermocouple Read Thermocouple ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | string | yes | 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| downsample_factor | integer | yes | Samples per min/max pair (1 = every sample returned) |
| sample_rate_hz | – | yes | Actual sample clock rate (None for one on-demand sample) |
| samples_per_channel | integer | yes | – |
| saved_to | – | yes | – |
| stats | array | yes | – |
| time_s | array | yes | Time of each returned point from the first sample |
| timestamp | string | yes | – |
| unit | string | yes | – |
| warnings | array | yes | NI-DAQmx warnings raised during the acquisition |
| waveforms | object | yes | 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 |
No examples provided.
reconnect Reconnect ~35
Close and re-open the connection to the instrument (e.g. after it was power cycled or a cable was re-plugged).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
set_outputs_safe Set Outputs Safe ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| digital_low | boolean | – | Also drive low every DO line this server drove (and the safe_do_lines option) |
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| timestamp | string | yes | – |
No examples provided.
write_analog Write Analog ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | One analog output, e.g. 'ao0' or 'Dev1/ao1' |
| voltage_v | number | yes | DC output voltage in V |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| timestamp | string | yes | – |
| voltage_v | number | yes | – |
No examples provided.
write_digital_lines Write Digital Lines ~132
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).
| Name | Type | Req | Description |
|---|---|---|---|
| levels | array | yes | One level for all lines, or one per line in order |
| lines | string | yes | Digital lines, e.g. 'port0/line0' or 'port0/line0:3' |
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | yes | – |
| timestamp | string | yes | – |
No examples provided.
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.