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.

IKA Hotplate & Overhead Stirrer

PYPI · LABMCP-IKA · SCANNED SEP 30

MCP server for IKA hotplate stirrers and overhead stirrers (NAMUR commands).

Available components

67 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 Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1458 tokens (~104/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the IKA Hotplate & Overhead Stirrer MCP server?

IKA Hotplate & Overhead Stirrer runs locally as a PyPI package, launched with uvx labmcp-ika. 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-ika

# add to Claude Code
claude mcp add k-dense-ai-labmcp-ika -- uvx labmcp-ika
// .cursor/mcp.json
{
  "mcpServers": {
    "k-dense-ai-labmcp-ika": {
      "command": "uvx",
      "args": [
        "labmcp-ika"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "k-dense-ai-labmcp-ika": {
      "command": "uvx",
      "args": [
        "labmcp-ika"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add k-dense-ai-labmcp-ika -- uvx labmcp-ika
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-ika": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-ika"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add k-dense-ai-labmcp-ika --command uvx --arg labmcp-ika
# ~/.hermes/config.yaml
mcp_servers:
  k-dense-ai-labmcp-ika:
    command: "uvx"
    args: ["labmcp-ika"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "k-dense-ai-labmcp-ika": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-ika"
      ]
    }
  }
}
# add to Vellum
assistant mcp add k-dense-ai-labmcp-ika -t stdio -c uvx -a labmcp-ika
// mcp.json
{
  "mcpServers": {
    "k-dense-ai-labmcp-ika": {
      "command": "uvx",
      "args": [
        "labmcp-ika"
      ]
    }
  }
}
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 −5
    • 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 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.1.0 → 0.1.1 functional
  • 26 Sept 26 57

    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-ika@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 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-ika-v0.1.1
Rekor log index 2969517330
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:d54dcd4340d2782af01fdb66b01744923599d5bcf9f42896435fc036eaec186a

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 · ~1,056 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
disable_watchdog ~47

Cancel watchdog mode 2 (OUT_WD2@0) and stop the background refresh. Watchdog mode 1 has no cancel command; this tool reports an error for it.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

enable_watchdog ~224

Arm the hotplate's communication watchdog (OUT_WD1@m / OUT_WD2@m). The server then re-sends the watchdog command in the background; if the computer, this server or the cable fails, the hotplate switches heating and stirring off (mode 1) or falls back to the given safety values (mode 2) after `timeout_s`. Note: stopping or reconnecting the server also stops the refresh, so the watchdog trips unless you enable it again. Mode 1 cannot be cancelled over the interface.

NameTypeReqDescription
modeinteger–1 = heater and motor off on timeout; 2 = fall back to the safety values below
safety_speed_rpmnumber–Mode 2 only: speed to fall back to (OUT_SP_42@)
safety_temperature_cnumber–Mode 2 only: setpoint to fall back to (OUT_SP_12@)
timeout_sinteger–Watchdog time (IKA allows 20-1500 s)

Structured output declared, but exposes no named fields.

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_status ~67

Read temperatures, stirring speed and setpoints. On hotplates: plate and external-probe temperature, temperature setpoint and the device's safety-circuit temperature. On overhead stirrers: PT1000 probe temperature, torque and the speed/torque limits set on the device.

Input schema present but exposes no named parameters.

NameTypeReqDescription
device_typestringyes–
external_temperature_c––External probe in the medium (IN_PV_1); None if unreadable, meaningless without a probe
heating_commanded––Last heater start/stop sent by this server; None = unknown
hotplate_temperature_c––Hotplate sensor (IN_PV_2)
probe_temperature_c––Overhead stirrer PT1000 probe (IN_PV_3)
safety_speed_rpm–––
safety_temperature_c––Safety-circuit temperature set on the device's dial (IN_SP_3)
speed_limit_rpm––Overhead stirrer speed limit set on the device
speed_rpmnumberyesActual stirring speed
speed_setpoint_rpmnumberyes–
stirring_commanded–yesLast start/stop sent by this server (the protocol cannot query it); None = unknown
temperature_setpoint_c–––
timestampstringyes–
torque_limit_ncm–––
torque_ncm––Overhead stirrer torque (IN_PV_5)
viscosity_trend––Hotplate viscosity trend (IN_PV_5, relative)
watchdog–––

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_speed ~82

Set the stirring speed setpoint (OUT_SP_4). Does not start the motor; if it is already running, the speed changes immediately. Refused above `max_speed_rpm` (and, on overhead stirrers, above the speed limit set on the device).

NameTypeReqDescription
speed_rpmnumberyesStirring speed setpoint in rpm
NameTypeReqDescription
reported_by_devicenumberyesSetpoint read back from the device after setting it
requestednumberyes–
timestampstringyes–
unitstringyes–
warning–––

No examples provided.

set_temperature ~93

Set the hotplate temperature setpoint (OUT_SP_1). With an external probe connected this is the target temperature of the medium. Does not start heating; if heating is already on, the plate starts moving to the new setpoint immediately. Refused above `max_temperature_c` or above the device's own safety-circuit temperature.

NameTypeReqDescription
temperature_cnumberyesTemperature setpoint in °C
NameTypeReqDescription
reported_by_devicenumberyesSetpoint read back from the device after setting it
requestednumberyes–
timestampstringyes–
unitstringyes–
warning–––

No examples provided.

start_heating ~64

Switch the hotplate heater on (START_1). It heats towards the current setpoint, which is checked against `max_temperature_c` first. Make sure the vessel and its contents can take the setpoint temperature and that nothing flammable is near the plate.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

start_stirring ~71

Start the stirring motor (START_4) at the current speed setpoint, which is checked against `max_speed_rpm` first. Make sure the stir bar or impeller is in place and the vessel is secured (a decoupled stir bar or an unclamped vessel can splash).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

stop_all ~46

Emergency stop: switch the heater off (hotplates) and stop the motor. Every stop command is sent even if one of them fails. Also ends a running `wait_for_temperature`.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

stop_heating ~37

Switch the hotplate heater off (STOP_1). Stirring continues. The plate stays hot for a long time after switching off.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

stop_stirring ~26

Stop the stirring motor (STOP_4). Heating (if on) continues.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

wait_for_temperature ~178

Poll a temperature until it is within `tolerance_c` of the target for `stable_for_s` seconds, or until `timeout_s` passes. Does not change anything on the device (start heating first). Returns whether the target was reached plus a short temperature trace. A stop command ends the wait early.

NameTypeReqDescription
poll_interval_snumber–Seconds between readings
sensorstring–'external' = probe in the medium (IN_PV_1, or IN_PV_3 on overhead stirrers)
stable_for_snumber–Must stay within tolerance this long
target_c––Temperature to wait for; default: the current setpoint
timeout_snumber–Give up after this many seconds
tolerance_cnumber–Accepted deviation in °C
NameTypeReqDescription
abortedbooleanyesTrue if a stop command ended the wait early
elapsed_snumberyes–
final_temperature_cnumberyes–
messagestringyes–
reachedbooleanyes–
sensorstringyes–
target_cnumberyes–
tolerance_cnumberyes–
tracearrayyes(seconds since start, °C), at most ~30 points

No examples provided.

Common questions

What is the IKA Hotplate & Overhead Stirrer MCP server?

IKA Hotplate & Overhead Stirrer is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-ika. MCP server for IKA hotplate stirrers and overhead stirrers (NAMUR commands). This page covers its PyPI package (labmcp-ika).

Is the IKA Hotplate & Overhead Stirrer MCP server safe to use?

IKA Hotplate & Overhead Stirrer scores 67 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 IKA Hotplate & Overhead Stirrer MCP server expose?

IKA Hotplate & Overhead Stirrer exposes 14 tools: get_connection_info, get_command_log, reconnect, get_status, set_temperature, and 9 more. Their descriptions and schemas cost roughly 1,056 tokens of context every time the server is loaded.

Is the IKA Hotplate & Overhead Stirrer MCP server still maintained?

IKA Hotplate & Overhead Stirrer 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 IKA Hotplate & Overhead Stirrer MCP server under?

IKA Hotplate & Overhead Stirrer 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.