Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Alicat Mass Flow & Pressure Controller

PYPI · LABMCP-ALICAT · SCANNED SEP 30

MCP server for Alicat mass flow and pressure meters/controllers.

Available components

69 Trust /100
Trust breakdown (7 categories)

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 Security49
  • Malware scan not yet available for this package.Unverified
  • 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
  • 2 of 17 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 Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1427 tokens (~101/item across 14 items; 14 tools + 0 resources), lean.Pass
  • 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 Coverage96
  • 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
Install

How do I install the Alicat Mass Flow & Pressure Controller MCP server?

Alicat Mass Flow & Pressure Controller runs locally as a PyPI package, launched with uvx labmcp-alicat. 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-alicat

# add to Claude Code
claude mcp add k-dense-ai-labmcp-alicat -- uvx labmcp-alicat
// .cursor/mcp.json
{
  "mcpServers": {
    "k-dense-ai-labmcp-alicat": {
      "command": "uvx",
      "args": [
        "labmcp-alicat"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "k-dense-ai-labmcp-alicat": {
      "command": "uvx",
      "args": [
        "labmcp-alicat"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add k-dense-ai-labmcp-alicat -- uvx labmcp-alicat
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-alicat": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-alicat"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add k-dense-ai-labmcp-alicat --command uvx --arg labmcp-alicat
# ~/.hermes/config.yaml
mcp_servers:
  k-dense-ai-labmcp-alicat:
    command: "uvx"
    args: ["labmcp-alicat"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "k-dense-ai-labmcp-alicat": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-alicat"
      ]
    }
  }
}
# add to Vellum
assistant mcp add k-dense-ai-labmcp-alicat -t stdio -c uvx -a labmcp-alicat
// mcp.json
{
  "mcpServers": {
    "k-dense-ai-labmcp-alicat": {
      "command": "uvx",
      "args": [
        "labmcp-alicat"
      ]
    }
  }
}
Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 −4
    • 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 +1
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 26 Sept 26 71

    First indexed and scored.

Diagnostics

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-alicat@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-alicat-v0.1.2
Rekor log index 2969517818
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:7fbc09471d6f0b36421dba1518333ad5f15b1329bd419942e31c8c6f98c808eb

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 17 packages
Packages resolved 17
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~959 tokens

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 →

Tool Tokens
close_valve ~64

Stop the flow: set the flow setpoint to 0 and hold all valves closed (Alicat HC). Safe to call at any time. On pressure controllers the pressure setpoint is left unchanged and the valves are held closed, trapping the current pressure.

Input schema present but exposes no named parameters.

NameTypeReqDescription
notesarrayyes–
reading–yes–
setpoint_zeroed–yesFlow setpoint set to 0 (None if not applicable)
valves_held_closedbooleanyes–

No examples provided.

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.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

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 ~46

Report model, serial number, firmware, calibration date, whether the device is a controller, the units of every data-frame field, the setpoint full scale and setpoint source.

Input schema present but exposes no named parameters.

NameTypeReqDescription
calibrated–yes–
data_frame_layoutstringyes–
fieldsarrayyes–
firmware–yes–
has_gas_selectbooleanyes–
is_controllerbooleanyes–
manufactured–yes–
model–yes–
notesarrayyes–
serial–yes–
setpoint––Current setpoint (controllers, 9v00+ firmware)
setpoint_full_scale––Largest setpoint the device accepts
setpoint_source––'serial/front panel' or 'analog' (10v05+). With 'analog', serial setpoints are ignored.
setpoint_unitstring––
unit_idstringyes–

No examples provided.

hold_valve ~58

Freeze the controller's valve(s) at their current position (HLD): closed-loop control stops, so flow will drift if upstream pressure changes. Use `resume_control` to release, or `close_valve` to shut off completely.

Input schema present but exposes no named parameters.

NameTypeReqDescription
fieldsarrayyesEvery field of the data frame, in device order
gas–––
layout_sourcestringyesHow fields were identified: '??D*' (device table) or 'fallback'
mass_flow–––
mass_flow_unitstring––
pressure–––
pressure_kindstring–'absolute', 'gauge' or 'differential'
pressure_unitstring––
rawstringyesThe raw data frame
setpoint––Controller setpoint (None on meters)
setpoint_unitstring––
statusarrayyesStatus / error codes reported with this frame
temperature–––
temperature_unitstring––
timestampstringyesUTC time the frame was read (ISO 8601)
unit_idstringyes–
valve_holdbooleanyesTrue if HLD is active (closed-loop control bypassed)
volumetric_flow–––
volumetric_flow_unitstring––

No examples provided.

list_gases ~43

List the gases installed on this mass flow device (number and short name), as used by `set_gas`. Liquid and pressure-only devices have no gas list.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

log_flow_series ~105

Record a time series of data frames (e.g. to check flow stability, settling after a setpoint change, or pressure drift). Returns every point plus mean/stdev/min/max of the mass flow (or the main measured quantity for non-flow devices).

NameTypeReqDescription
countinteger–Number of readings
interval_snumber–Seconds between readings
save_path––Optional new .csv file for the full series (an existing file is not overwritten)
NameTypeReqDescription
countintegeryes–
maximum–yes–
mean–yes–
minimum–yes–
pointsarrayyes–
quantitystringyesWhich field the statistics describe (mass_flow if present)
saved_to–––
stdev–yes–
unitstringyes–

No examples provided.

read_flow ~46

Read the live data frame: mass flow, volumetric flow, pressure, temperature, setpoint (controllers), active gas and any status codes, each with the device's engineering units.

Input schema present but exposes no named parameters.

NameTypeReqDescription
fieldsarrayyesEvery field of the data frame, in device order
gas–––
layout_sourcestringyesHow fields were identified: '??D*' (device table) or 'fallback'
mass_flow–––
mass_flow_unitstring––
pressure–––
pressure_kindstring–'absolute', 'gauge' or 'differential'
pressure_unitstring––
rawstringyesThe raw data frame
setpoint––Controller setpoint (None on meters)
setpoint_unitstring––
statusarrayyesStatus / error codes reported with this frame
temperature–––
temperature_unitstring––
timestampstringyesUTC time the frame was read (ISO 8601)
unit_idstringyes–
valve_holdbooleanyesTrue if HLD is active (closed-loop control bypassed)
volumetric_flow–––
volumetric_flow_unitstring––

No examples provided.

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.

resume_control ~47

Cancel any valve hold and resume closed-loop control to the current setpoint. Flow restarts immediately if the setpoint is not 0 (check it with `read_flow` first).

Input schema present but exposes no named parameters.

NameTypeReqDescription
fieldsarrayyesEvery field of the data frame, in device order
gas–––
layout_sourcestringyesHow fields were identified: '??D*' (device table) or 'fallback'
mass_flow–––
mass_flow_unitstring––
pressure–––
pressure_kindstring–'absolute', 'gauge' or 'differential'
pressure_unitstring––
rawstringyesThe raw data frame
setpoint––Controller setpoint (None on meters)
setpoint_unitstring––
statusarrayyesStatus / error codes reported with this frame
temperature–––
temperature_unitstring––
timestampstringyesUTC time the frame was read (ISO 8601)
unit_idstringyes–
valve_holdbooleanyesTrue if HLD is active (closed-loop control bypassed)
volumetric_flow–––
volumetric_flow_unitstring––

No examples provided.

set_flow_setpoint ~103

Change the controller setpoint: starts, changes or stops gas flow (or sets the target pressure on a pressure controller). 0 stops flow and closes the valve on a flow controller. Negative values only work on bidirectional controllers. Refused on meters, above the `max_setpoint` limit, and above the device's full scale.

NameTypeReqDescription
setpointnumberyesNew setpoint in the controller's setpoint units (see get_device_info)
NameTypeReqDescription
accepted_setpointnumberyesSetpoint the controller reports it is now using
messagestringyes–
requestednumberyes–
unitstringyes–

No examples provided.

set_gas ~171

Select the gas calibration the mass flow device uses (Gas Select). This changes how flow is computed, so do it with the setpoint at 0. Only gases installed on the device work (see `list_gases`); corrosive gases need anti-corrosive (S-series) hardware.

NameTypeReqDescription
gasstringyesGas short name or number, e.g. 'N2' (8), 'Air' (0), 'O2' (11), 'CO2' (4), 'Ar' (1), 'He' (7), 'H2' (6), 'CH4' (2); COMPOSER mixes are 236-255
save_as_power_upboolean–Also make it the power-up gas (10v05+)
NameTypeReqDescription
gasstringyes–
gas_numberintegeryes–
saved_as_power_upbooleanyes–

No examples provided.

tare_flow ~66

Tare (zero) the flow reading. ONLY run with no flow through the device: upstream shut off or controller setpoint 0, with the line at its normal operating pressure. Refused if the setpoint is not 0 or a significant flow is still being measured.

Input schema present but exposes no named parameters.

NameTypeReqDescription
fieldsarrayyesEvery field of the data frame, in device order
gas–––
layout_sourcestringyesHow fields were identified: '??D*' (device table) or 'fallback'
mass_flow–––
mass_flow_unitstring––
pressure–––
pressure_kindstring–'absolute', 'gauge' or 'differential'
pressure_unitstring––
rawstringyesThe raw data frame
setpoint––Controller setpoint (None on meters)
setpoint_unitstring––
statusarrayyesStatus / error codes reported with this frame
temperature–––
temperature_unitstring––
timestampstringyesUTC time the frame was read (ISO 8601)
unit_idstringyes–
valve_holdbooleanyesTrue if HLD is active (closed-loop control bypassed)
volumetric_flow–––
volumetric_flow_unitstring––

No examples provided.

tare_pressure ~89

Tare a pressure reading. Requires no flow and the device OPEN TO ATMOSPHERE (gauge), or no flow and an unpressurised process line (absolute, barometer-equipped devices only).

NameTypeReqDescription
kindstring–'gauge' zeroes a gauge/differential sensor; 'absolute' aligns the absolute sensor to the built-in barometer (barometer option required)
NameTypeReqDescription
fieldsarrayyesEvery field of the data frame, in device order
gas–––
layout_sourcestringyesHow fields were identified: '??D*' (device table) or 'fallback'
mass_flow–––
mass_flow_unitstring––
pressure–––
pressure_kindstring–'absolute', 'gauge' or 'differential'
pressure_unitstring––
rawstringyesThe raw data frame
setpoint––Controller setpoint (None on meters)
setpoint_unitstring––
statusarrayyesStatus / error codes reported with this frame
temperature–––
temperature_unitstring––
timestampstringyesUTC time the frame was read (ISO 8601)
unit_idstringyes–
valve_holdbooleanyesTrue if HLD is active (closed-loop control bypassed)
volumetric_flow–––
volumetric_flow_unitstring––

No examples provided.

Common questions

What is the Alicat Mass Flow & Pressure Controller MCP server?

Alicat Mass Flow & Pressure Controller is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-alicat. MCP server for Alicat mass flow and pressure meters/controllers. This page covers its PyPI package (labmcp-alicat).

Is the Alicat Mass Flow & Pressure Controller MCP server safe to use?

Alicat Mass Flow & Pressure Controller scores 69 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 Alicat Mass Flow & Pressure Controller MCP server expose?

Alicat Mass Flow & Pressure Controller exposes 14 tools: get_connection_info, get_command_log, reconnect, read_flow, get_device_info, and 9 more. Their descriptions and schemas cost roughly 959 tokens of context every time the server is loaded.

Is the Alicat Mass Flow & Pressure Controller MCP server still maintained?

Alicat Mass Flow & Pressure Controller 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 Alicat Mass Flow & Pressure Controller MCP server under?

Alicat Mass Flow & Pressure Controller 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.