# SiLA 2 Bridge (pypi · labmcp-sila2)

MCP bridge to any SiLA 2 server (lab-automation standard).

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- pypi · `labmcp-sila2`: 68/100 (this document), [markdown](https://verifymcp.io/servers/k-dense-ai-labmcp-sila2/labmcp-sila2.md), [page](https://verifymcp.io/servers/k-dense-ai-labmcp-sila2/labmcp-sila2)

## Channel facts

- Registry: `pypi`
- Package: `labmcp-sila2`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-30.

- **Supply Chain Security**: 49/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 3 of 25 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1346 tokens (~103/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SiLA 2 Bridge MCP server?

SiLA 2 Bridge runs locally as a PyPI package, launched with uvx labmcp-sila2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add k-dense-ai-labmcp-sila2 -- uvx labmcp-sila2
```

### Cursor

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-sila2": {
      "command": "uvx",
      "args": [
        "labmcp-sila2"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k-dense-ai-labmcp-sila2": {
      "command": "uvx",
      "args": [
        "labmcp-sila2"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k-dense-ai-labmcp-sila2 -- uvx labmcp-sila2
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-sila2": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-sila2"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k-dense-ai-labmcp-sila2 --command uvx --arg labmcp-sila2
```

### Hermes

```yaml
mcp_servers:
  k-dense-ai-labmcp-sila2:
    command: "uvx"
    args: ["labmcp-sila2"]
```

### Netclaw

```json
{
  "McpServers": {
    "k-dense-ai-labmcp-sila2": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-sila2"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k-dense-ai-labmcp-sila2 -t stdio -c uvx -a labmcp-sila2
```

### Other

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-sila2": {
      "command": "uvx",
      "args": [
        "labmcp-sila2"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, +29)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 39, 0)

- [functional] Package version: 0.1.1 → 0.1.2

### 2026-09-26 (score 39)

First indexed and scored.

## MCP tools (13)

### `get_connection_info` (~40 tokens)

Get Connection Info

Report which instrument is connected (identity, address, simulated or real),
whether the server is read-only, and the active safety limits. Call this first.

### `get_command_log` (~46 tokens)

Get Command Log

Return the most recent raw commands sent to / replies received from the
instrument (newest last). Useful for debugging and for recording what was done.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (array)

### `reconnect` (~35 tokens)

Reconnect

Close and re-open the connection to the instrument (e.g. after it was power
cycled or a cable was re-plugged).

### `discover_servers` (~69 tokens)

Discover Servers

Find SiLA 2 servers on the local network with SiLA Server Discovery (mDNS `_sila._tcp`). Lists
name, UUID, address and port of each without connecting. Does not need a configured server.

Input parameters:

- `timeout_s` (number): How long to listen for mDNS announcements

Output parameters:

- `duration_s` (number)
- `servers` (array)
- `simulated` (boolean)
- `timestamp` (string)

### `get_server_info` (~48 tokens)

Get Server Info

Identify the connected SiLA server (name, type, UUID, version, vendor, description), list its
features, and say whether commands can be cancelled and which commands this bridge may call.

Output parameters:

- `address` (string)
- `cancellation_supported` (boolean): Server implements org.silastandard/core.commands/CancelController/v1
- `command_allowlist`: Commands this bridge may call (None: all)
- `features` (array): Fully qualified identifiers of the implemented features
- `security` (string)
- `server_description`
- `server_name`
- `server_type`
- `server_uuid`
- `server_version`
- `simulated` (boolean)
- `timestamp` (string)
- `vendor_url`

### `list_features` (~110 tokens)

List Features

Describe the server's features from their Feature Definitions: every command (observable or
not, parameters, responses, intermediate responses, defined errors, and whether the allow-list
permits calling it) and every property, with types rendered as JSON-schema-like dicts including
units and constraints.

Input parameters:

- `feature`: Only this feature (identifier); default all
- `include_core` (boolean): Include the SiLAService core feature
- `include_fdl` (boolean): Also return the raw Feature Definition XML

Output parameters:

- `features` (array): Per feature: commands (parameters/responses as JSON-schema-like dicts), properties, errors
- `timestamp` (string)

### `get_property` (~81 tokens)

Get Property

Read the current value of a SiLA property (for observable properties: the first value of a
subscription).

Input parameters:

- `feature` (string, required): Feature identifier, e.g. 'TemperatureController'
- `metadata`: SiLA client metadata, e.g. {'LockController.LockIdentifier': '...'} (if the server requires it)
- `property` (string, required)

Output parameters:

- `feature` (string)
- `observable` (boolean)
- `property` (string)
- `timestamp` (string)
- `type` (object): JSON-schema-like description incl. unit (x-unit) and constraints
- `value`

### `subscribe_property` (~136 tokens)

Subscribe Property

Collect a property's values for `duration_s` seconds (SiLA subscription for observable
properties, polling otherwise) and summarise them (e.g. watch a temperature settle).

Input parameters:

- `duration_s` (number): How long to collect updates
- `feature` (string, required): Feature identifier, e.g. 'TemperatureController'
- `max_updates` (integer): Stop after this many updates
- `metadata`: SiLA client metadata, e.g. {'LockController.LockIdentifier': '...'} (if the server requires it)
- `poll_interval_s` (number): Polling interval for unobservable properties
- `property` (string, required)

Output parameters:

- `feature` (string)
- `mode` (string): subscription (observable property) or polling
- `n_updates` (integer)
- `property` (string)
- `stats`: min/max/mean/first/last for numeric values
- `timestamp` (string)
- `updates` (array)

### `call_command` (~178 tokens)

Call Command

Run a SiLA command. This may physically act on the device (move, dispense, heat, shake, open
doors): tell the user what will happen first. Parameters are validated against the Feature
Definition before anything is sent, and the command must be in the allow-list if one is set.
Unobservable commands return their responses; observable ones return an `execution_id`.

Input parameters:

- `command` (string, required): Command identifier
- `feature` (string, required): Feature identifier, e.g. 'TemperatureController'
- `metadata`: SiLA client metadata, e.g. {'LockController.LockIdentifier': '...'} (if the server requires it)
- `parameters` (object): Parameter identifier -> value, as described by list_features
- `wait_s` (number): Observable commands: wait up to this long for completion (0 = return at once)

Output parameters:

- `command` (string)
- `done` (boolean)
- `error`
- `execution_id`: For observable commands: use with get_command_status
- `feature` (string)
- `observable` (boolean)
- `progress`
- `responses`
- `status`
- `timestamp` (string)
- `warnings` (array)

### `get_command_status` (~52 tokens)

Get Command Status

Status of an observable command started with `call_command`: waiting / running /
finishedSuccessfully / finishedWithError, progress, estimated remaining time and the latest
intermediate response.

Input parameters:

- `execution_id` (string, required)

Output parameters:

- `command` (string)
- `done` (boolean)
- `estimated_remaining_s`
- `execution_id` (string)
- `feature` (string)
- `latest_intermediate_response`
- `lifetime_of_execution_s`: How long the server keeps the result
- `parameters`
- `progress`: 0-1, if the server reports it
- `started` (string)
- `status` (string): waiting, running, finishedSuccessfully or finishedWithError
- `timestamp` (string)

### `get_command_result` (~46 tokens)

Get Command Result

Responses of a finished observable command, or the SiLA execution error it finished with.
Fails with a clear message if the command is still running.

Input parameters:

- `execution_id` (string, required)

Output parameters:

- `command` (string)
- `error`
- `execution_id` (string)
- `feature` (string)
- `responses`
- `status` (string)
- `success` (boolean)
- `timestamp` (string)

### `list_executions` (~26 tokens)

List Executions

All observable command executions started in this session, newest last, with their status.

Output parameters:

- `result` (array)

### `cancel_command` (~90 tokens)

Cancel Command

Cancel a running observable command, or all commands, through SiLA's CancelController feature.
Always available (even read-only). If the server has no CancelController, this explains that and
points to the device's own stop command.

Input parameters:

- `all_commands` (boolean): Cancel every running command on the server
- `execution_id`: Execution to cancel; omit (or all_commands=true) to cancel everything

Output parameters:

- `execution_id`
- `message` (string)
- `status_after`
- `supported` (boolean)
- `timestamp` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k-dense-ai-labmcp-sila2/labmcp-sila2#diagnostics

## Score history

- 2026-09-30: 68
- 2026-09-29: 68
- 2026-09-28: 68
- 2026-09-27: 39
- 2026-09-26: 39

## Common questions

### What is the SiLA 2 Bridge MCP server?

SiLA 2 Bridge is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-sila2. MCP bridge to any SiLA 2 server (lab-automation standard). This page covers its PyPI package (labmcp-sila2).

### Is the SiLA 2 Bridge MCP server safe to use?

SiLA 2 Bridge scores 68 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 SiLA 2 Bridge MCP server expose?

SiLA 2 Bridge exposes 13 tools: get_connection_info, get_command_log, reconnect, discover_servers, get_server_info, and 8 more. Their descriptions and schemas cost roughly 957 tokens of context every time the server is loaded.

### Is the SiLA 2 Bridge MCP server still maintained?

SiLA 2 Bridge 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 SiLA 2 Bridge MCP server under?

SiLA 2 Bridge 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.

## Links

- PyPI project: https://pypi.org/project/labmcp-sila2/
- Socket report: https://socket.dev/pypi/package/labmcp-sila2
- Repository: https://github.com/K-Dense-AI/lab-instrument-mcps
- Website: https://github.com/K-Dense-AI/lab-instrument-mcps/tree/main/servers/protocols/sila2
- Changelog RSS feed: https://verifymcp.io/servers/k-dense-ai-labmcp-sila2/labmcp-sila2.xml
- Changelog JSON feed: https://verifymcp.io/servers/k-dense-ai-labmcp-sila2/labmcp-sila2.json
- HTML version of this page: https://verifymcp.io/servers/k-dense-ai-labmcp-sila2/labmcp-sila2