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.

Senseca PRO thermometer

PYPI · MCP-SERVER-SENSECA-PRO

Live readings from Senseca PRO 111/115 Pt100 thermometers via USB (unofficial)

+18 this week 80 Trust /100

Last scanned (7 hours ago)

Scores higher than 80% of PyPI servers

Category IoT and Hardware

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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to shaag7967/mcp-server-senseca-pro). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 224 tokens (~56/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 +1

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

  • 2 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 30 Oct 26 +1

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

  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 28 Oct 26 77

    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 5 Nov 2026 · Analysed pypi/mcp-server-senseca-pro@0.1.1

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 shaag7967/mcp-server-senseca-pro
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/shaag7967/mcp-server-senseca-pro/.github/workflows/publish.yml@refs/tags/v0.1.1
Rekor log index 3546448696
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:9a3b32923bd1c89d46ab171024510ebb7c5cdc2eb3a936ee22d37a8d08f5bc60

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~154 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_device_info ~25

Instrument model, serial number, firmware, clock (UTC) and battery level.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

read_resistance ~31

Read the current Pt100 probe resistance in ohm (about 100 ohm at 0 °C).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

read_temperature ~24

Read the current temperature from the Pt100 probe, with unit and UTC timestamp.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

sample_temperature ~74

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).

NameTypeReqDescription
duration_snumber––
interval_snumber––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Senseca PRO thermometer MCP server?

Senseca PRO thermometer runs locally as a PyPI package, launched with uvx mcp-server-senseca-pro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-server-senseca-pro

# add to Claude Code
claude mcp add shaag7967-mcp-server-senseca-pro -- uvx mcp-server-senseca-pro
Common questions

What is the Senseca PRO thermometer MCP server?

Senseca PRO thermometer is an MCP server listed in the public MCP registry as io.github.shaag7967/mcp-server-senseca-pro. Live readings from Senseca PRO 111/115 Pt100 thermometers via USB (unofficial). This page covers its PyPI package (mcp-server-senseca-pro).

Is the Senseca PRO thermometer MCP server safe to use?

Senseca PRO thermometer scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Senseca PRO thermometer MCP server expose?

Senseca PRO thermometer exposes 4 tools: read_temperature, read_resistance, sample_temperature, get_device_info. Their descriptions and schemas cost roughly 154 tokens of context every time the server is loaded.

Is the Senseca PRO thermometer MCP server still maintained?

Senseca PRO thermometer is still listed as active in the MCP registry. We last reached this channel on 5 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 Senseca PRO thermometer MCP server under?

Senseca PRO thermometer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.