Pfeiffer Vacuum Gauge Controller
PYPI · LABMCP-PFEIFFER-TPG
MCP server for Pfeiffer Vacuum TPG 361/362/366 and TPG 261/262 gauge controllers.
Available components
Last scanned (14 hours ago)
Scores higher than 98% of PyPI servers
Category IoT and Hardware
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
- 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 55 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Nov 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −17
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.90 functional
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 21 Nov 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 | Known build tool | 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 →
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_errors 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
log_pressure_series 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.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | – | – | Channels to include (default: all) |
| duration_s | number | – | How long to log (at most 2 h per call) |
| interval_s | number | – | Seconds between readings |
| max_points | integer | – | Points returned per channel |
| save_path | – | – | Optional CSV file for every reading |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| count | integer | yes | – |
| duration_s | number | yes | – |
| interval_s | number | yes | – |
| pressures_mbar | object | yes | Channel -> mbar values (downsampled) |
| saved_to | – | – | – |
| started | string | yes | – |
| stats | array | yes | – |
| times_s | array | yes | Seconds since start (downsampled to max_points) |
No examples provided.
read_all_pressures 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.
| Name | Type | Req | Description |
|---|---|---|---|
| readings | array | yes | – |
| timestamp | string | yes | – |
| unit | string | yes | – |
No examples provided.
read_pressure Read Pressure ~39
Read one gauge channel: status, pressure in the display unit and in mbar.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | – | Measurement channel (gauge) number |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | – |
| pressure | – | yes | Pressure in `unit`; null unless status is ok |
| pressure_mbar | – | yes | Pressure converted to mbar (null for V or invalid) |
| raw_value | number | yes | Value sent by the controller (range limit when under/overrange) |
| status | string | yes | ok, underrange, overrange, sensor error, sensor off, no sensor, ... |
| timestamp | string | yes | – |
| unit | string | yes | Controller display unit: mbar, hPa, Pa, Torr, micron or V |
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_gauge_power 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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Channel of the ionisation gauge |
| on | boolean | yes | True = switch the gauge on, False = off |
| reference_channel | – | – | Another gauge on the same vacuum (e.g. a Pirani) used to check the pressure |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
set_unit Set Unit ~59
Change the pressure unit used on the display and interface (UNI). Readings in mbar are always included regardless of this setting.
| Name | Type | Req | Description |
|---|---|---|---|
| unit | string | yes | Display/interface unit (TPG 26x: mbar, Pa or Torr only) |
Structured output declared, but exposes no named fields.
No examples provided.
switch_gauge_off 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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | integer | yes | Channel of the ionisation gauge to switch off |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
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
claude mcp add k-dense-ai-labmcp-pfeiffer-tpg -- uvx labmcp-pfeiffer-tpg
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 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 21 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 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.
What did VerifyMCP test on the Pfeiffer Vacuum Gauge Controller MCP server?
VerifyMCP ran 16 checks on Pfeiffer Vacuum Gauge Controller, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.