read_temperature
Read the current temperature from the Pt100 probe, with unit and UTC timestamp.
Takes no parameters.

io.github.shaag7967Published by GitHub account shaag7967v0.1.1Updated Nov 3, 2026
Live readings from Senseca PRO 111/115 Pt100 thermometers via USB (unofficial)
Reads live temperature and Pt100 resistance from a Senseca PRO 111/115 USB thermometer, with sampling and device info.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
An MCP server that lets AI assistants read live measurements from a Senseca PRO 111 / PRO 115 handheld Pt100 thermometer connected via USB.
Unofficial project, not affiliated with or endorsed by Senseca. Tested with a PRO 111, firmware V1.4.3.0, interface protocol V1.0.0.1.
With --allow-write two more tools are available:
The server cannot change calibration or adjustment data; the instrument does not offer that over its serial interface.
dialout group (sudo usermod -aG dialout $USER, then log in again).COMx or /dev/cu.usbmodem….Auto-detection looks for USB ID 0483:5740 and only accepts a port whose device reports
manufacturer senseca. If several instruments are connected, set the port explicitly; on Linux
prefer the stable /dev/serial/by-id/… path.
Only one program can use the serial port at a time. Close ProXware or terminal programs while the server is running.
To check a real instrument, connect it and run:
The script only sends read commands. See --help for the PIN test.
The serial protocol is described in docs/protocol.md.
MIT
Source: README.md at commit 26bc87f
Read the current temperature from the Pt100 probe, with unit and UTC timestamp.
Takes no parameters.
Read the current Pt100 probe resistance in ohm (about 100 ohm at 0 °C).
Takes no parameters.
Record temperature readings over a period and return statistics plus all samples. Args: duration_s: Recording time in seconds (max 600). interval_s: Time between readings in seconds (min 0.5, the instrument's update rate).
duration_sinterval_sInstrument model, serial number, firmware, clock (UTC) and battery level.
Takes no parameters.
90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
claude mcp add senseca-pro -- uvx mcp-server-senseca-pro{ "mcpServers": { "senseca-pro": { "command": "uvx", "args": ["mcp-server-senseca-pro"] } }}uv syncuv run pytest # tests use a simulated instrumentnpx @modelcontextprotocol/inspector uv run mcp-server-senseca-pro # try the tools interactivelyuv run python scripts/hardware_test.py # read-only checks, no interactionuv run python scripts/hardware_test.py --reconnect # also unplug/replug USB when asked