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.

Pfeiffer Vacuum Gauge Controller

PYPI · LABMCP-PFEIFFER-TPG · SCANNED SEP 30

MCP server for Pfeiffer Vacuum TPG 361/362/366 and TPG 261/262 gauge controllers.

68 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 Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1087 tokens (~98/item across 11 items; 11 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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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
Install

How do I install the Pfeiffer Vacuum Gauge Controller MCP server?

Pfeiffer Vacuum Gauge Controller runs locally as a PyPI package, launched with uvx labmcp-pfeiffer-tpg. 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-pfeiffer-tpg

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

  • 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-pfeiffer-tpg@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-pfeiffer-tpg-v0.1.2
Rekor log index 2969518134
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:79ba6a8807ad75321d0d4513066ac1a085945a9e38f7f74f8e288ed2a9866532

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 · 11 exposed · ~713 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
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_errors ~41

Read (and clear) the controller's ERROR word: controller error, no hardware, inadmissible parameter or syntax error. An empty list means no error.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_gauge_types ~46

List the gauge connected to each channel (TID), what kind it is, and whether it is an ionisation gauge that is currently switched on or off (SEN).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

log_pressure_series ~155

Log pressures at a fixed interval (e.g. a pump-down curve, leak-up/rate-of-rise test or bake-out). Returns per-channel statistics in log-space plus a downsampled series; the full series can be written to a new CSV file (an existing file is never overwritten). Bounded by `max_log_duration_s` and 2 h per call.

NameTypeReqDescription
channels––Channels to include (default: all)
duration_snumber–How long to log (at most 2 h per call)
interval_snumber–Seconds between readings
max_pointsinteger–Points returned per channel
save_path––Optional CSV file for every reading
NameTypeReqDescription
channelsarrayyes–
countintegeryes–
duration_snumberyes–
interval_snumberyes–
pressures_mbarobjectyesChannel -> mbar values (downsampled)
saved_to–––
startedstringyes–
statsarrayyes–
times_sarrayyesSeconds since start (downsampled to max_points)

No examples provided.

read_all_pressures ~27

Read every channel of the controller at once (PRX), with status per channel.

Input schema present but exposes no named parameters.

NameTypeReqDescription
readingsarrayyes–
timestampstringyes–
unitstringyes–

No examples provided.

read_pressure ~39

Read one gauge channel: status, pressure in the display unit and in mbar.

NameTypeReqDescription
channelinteger–Measurement channel (gauge) number
NameTypeReqDescription
channelintegeryes–
pressure–yesPressure in `unit`; null unless status is ok
pressure_mbar–yesPressure converted to mbar (null for V or invalid)
raw_valuenumberyesValue sent by the controller (range limit when under/overrange)
statusstringyesok, underrange, overrange, sensor error, sensor off, no sensor, ...
timestampstringyes–
unitstringyesController display unit: mbar, hPa, Pa, Torr, micron or V

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.

set_gauge_power ~160

Switch an ionisation gauge (IKR, PKR, PBR, IMR) on or off (SEN). Switching a hot or cold cathode gauge on at high pressure can burn out the filament or contaminate the gauge, so switching ON is refused unless a valid reading from this gauge or `reference_channel` is at or below `max_switch_on_pressure_mbar`. Switching off may trip setpoint relays used as interlocks.

NameTypeReqDescription
channelintegeryesChannel of the ionisation gauge
onbooleanyesTrue = switch the gauge on, False = off
reference_channel––Another gauge on the same vacuum (e.g. a Pirani) used to check the pressure
NameTypeReqDescription
resultarrayyes–

No examples provided.

set_unit ~59

Change the pressure unit used on the display and interface (UNI). Readings in mbar are always included regardless of this setting.

NameTypeReqDescription
unitstringyesDisplay/interface unit (TPG 26x: mbar, Pa or Torr only)

Structured output declared, but exposes no named fields.

No examples provided.

switch_gauge_off ~65

Switch an ionisation gauge off (e.g. before venting, or if the pressure is rising). Always allowed. Note that setpoint relays assigned to this channel may change state.

NameTypeReqDescription
channelintegeryesChannel of the ionisation gauge to switch off
NameTypeReqDescription
resultarrayyes–

No examples provided.

Common questions

What is the Pfeiffer Vacuum Gauge Controller MCP server?

Pfeiffer Vacuum Gauge Controller is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-pfeiffer-tpg. MCP server for Pfeiffer Vacuum TPG 361/362/366 and TPG 261/262 gauge controllers. This page covers its PyPI package (labmcp-pfeiffer-tpg).

Is the Pfeiffer Vacuum Gauge Controller MCP server safe to use?

Pfeiffer Vacuum Gauge Controller scores 68 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 Pfeiffer Vacuum Gauge Controller MCP server expose?

Pfeiffer Vacuum Gauge Controller exposes 11 tools: get_connection_info, get_command_log, reconnect, read_pressure, read_all_pressures, and 6 more. Their descriptions and schemas cost roughly 713 tokens of context every time the server is loaded.

Is the Pfeiffer Vacuum Gauge Controller MCP server still maintained?

Pfeiffer Vacuum Gauge 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 Pfeiffer Vacuum Gauge Controller MCP server under?

Pfeiffer Vacuum Gauge 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.