Modbus TCP/RTU Device
PYPI · LABMCP-MODBUS · SCANNED SEP 30
MCP server for Modbus TCP/RTU devices with typed, scaled register maps and per-point limits.
Available components
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 19 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1277 tokens (~106/item across 12 items; 12 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the Modbus TCP/RTU Device MCP server?
Modbus TCP/RTU Device runs locally as a PyPI package, launched with uvx labmcp-modbus. 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-modbus
claude mcp add k-dense-ai-labmcp-modbus -- uvx labmcp-modbus
{
"mcpServers": {
"k-dense-ai-labmcp-modbus": {
"command": "uvx",
"args": [
"labmcp-modbus"
]
}
}
} {
"servers": {
"k-dense-ai-labmcp-modbus": {
"command": "uvx",
"args": [
"labmcp-modbus"
]
}
}
} codex mcp add k-dense-ai-labmcp-modbus -- uvx labmcp-modbus
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"k-dense-ai-labmcp-modbus": {
"type": "local",
"command": [
"uvx",
"labmcp-modbus"
],
"enabled": true
}
}
} openclaw mcp add k-dense-ai-labmcp-modbus --command uvx --arg labmcp-modbus
mcp_servers:
k-dense-ai-labmcp-modbus:
command: "uvx"
args: ["labmcp-modbus"] {
"McpServers": {
"k-dense-ai-labmcp-modbus": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"labmcp-modbus"
]
}
}
} assistant mcp add k-dense-ai-labmcp-modbus -t stdio -c uvx -a labmcp-modbus
{
"mcpServers": {
"k-dense-ai-labmcp-modbus": {
"command": "uvx",
"args": [
"labmcp-modbus"
]
}
}
} 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +29
- 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 −33
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.2 → 0.1.3 functional
- 26 Sept 26 72
First indexed and scored.
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-modbus@0.1.3
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-modbus-v0.1.3 |
| Rekor log index | 2969518363 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:942afc9b622655096ac6c19001b7472c3d6ef34572560957df0aecf655ed7f56 |
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 19 packages
| Packages resolved | 19 |
|---|---|
| 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.
list_points List Points ~52
Describe the loaded register map: device, every named point (table, 0-based address, type, scaling, unit, writable, min/max, enum) and the safe-state steps. Works without a connection.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| device | object | yes | – |
| error | – | – | – |
| loaded | boolean | yes | – |
| points | array | yes | – |
| raw_writes | boolean | yes | – |
| safe_state | array | yes | – |
| source | – | yes | – |
| unit_id | – | yes | – |
No examples provided.
read_coils Read Coils ~49
Read coils (FC01): single-bit outputs such as run/stop or relay states.
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | 0-based start address |
| count | integer | – | Number of coils |
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | – |
| count | integer | yes | – |
| table | string | yes | – |
| timestamp | string | yes | – |
| values | array | yes | – |
No examples provided.
read_discrete_inputs Read Discrete Inputs ~52
Read discrete inputs (FC02): single-bit, read-only status such as alarms or limit switches.
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | 0-based start address |
| count | integer | – | Number of inputs |
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | – |
| count | integer | yes | – |
| table | string | yes | – |
| timestamp | string | yes | – |
| values | array | yes | – |
No examples provided.
read_points Read Points ~69
Read named points from the register map, decoded and scaled into engineering units (e.g. process_temperature = 25.1 °C). A point that cannot be read gets an `error` instead of failing the whole call.
| Name | Type | Req | Description |
|---|---|---|---|
| names | – | – | Point names from list_points; omit for all points |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
read_registers Read Registers ~140
Read raw holding or input registers (unsigned 16-bit), optionally decoded as int16, 32-bit or 64-bit values. For exploring a device; prefer read_points when a register map describes it.
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | 0-based start address |
| byte_order | string | – | big = standard Modbus byte order |
| count | integer | – | Number of registers |
| decode_as | string | – | Also decode the registers as this type |
| table | string | – | holding (FC03) or input (FC04) |
| word_order | string | – | 32/64-bit: big = high word first |
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | – |
| count | integer | yes | – |
| decoded | – | – | Values decoded with decode_as ("nan"/"inf"/"-inf" for non-finite floats) |
| hex | array | yes | – |
| registers | array | yes | Raw unsigned 16-bit values |
| table | string | yes | – |
| timestamp | string | yes | – |
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.
write_coil Write Coil ~74
Switch one raw coil (FC05). Coils often start or stop equipment (heaters, pumps, motors); mapped coils are refused here (use write_point).
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | 0-based coil address |
| value | boolean | yes | true = ON (0xFF00), false = OFF |
Structured output declared, but exposes no named fields.
No examples provided.
write_point Write Point ~125
Write a named point from the register map (setpoint, mode, output enable...). The value is checked against the point's writable flag, min/max or enum BEFORE sending, converted to raw registers, written, then read back. Changing setpoints and outputs acts on real equipment. If the write succeeds but the read-back fails, `read_back_error` says why.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A writable point from list_points |
| value | – | yes | Engineering value (e.g. 37.5 for °C), true/false, or an enum label |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | boolean | yes | True if the read-back equals the written value |
| name | string | yes | – |
| read_back | – | yes | – |
| read_back_error | – | – | Why the value could not be read back (it WAS written) |
| requested | – | yes | – |
| timestamp | string | yes | – |
| unit | string | yes | – |
| written | – | yes | Value after rounding to the register's resolution |
No examples provided.
write_register Write Register ~88
Write one raw holding register (FC06). No scaling or limits are applied, so only use it for addresses the register map does not describe (mapped addresses are refused: use write_point). Returns a read-back if the register is readable.
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | 0-based holding-register address |
| value | integer | yes | Raw value (negative = int16 two's complement) |
Structured output declared, but exposes no named fields.
No examples provided.
write_registers Write Registers ~70
Write consecutive raw holding registers (FC16), e.g. both halves of a 32-bit value. No scaling or limits are applied; mapped addresses are refused (use write_point).
| Name | Type | Req | Description |
|---|---|---|---|
| address | integer | yes | 0-based start address |
| values | array | yes | Raw 16-bit values |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Modbus TCP/RTU Device MCP server?
Modbus TCP/RTU Device is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-modbus. MCP server for Modbus TCP/RTU devices with typed, scaled register maps and per-point limits. This page covers its PyPI package (labmcp-modbus).
Is the Modbus TCP/RTU Device MCP server safe to use?
Modbus TCP/RTU Device scores 69 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 Modbus TCP/RTU Device MCP server expose?
Modbus TCP/RTU Device exposes 12 tools: get_connection_info, get_command_log, reconnect, list_points, read_points, and 7 more. Their descriptions and schemas cost roughly 840 tokens of context every time the server is loaded.
Is the Modbus TCP/RTU Device MCP server still maintained?
Modbus TCP/RTU Device 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 Modbus TCP/RTU Device MCP server under?
Modbus TCP/RTU Device 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.