SiLA 2 Bridge
PYPI · LABMCP-SILA2
MCP bridge to any SiLA 2 server (lab-automation standard).
Available components
Last scanned (16 hours ago)
Scores higher than 80% of PyPI servers
Category Health and Science
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
- 3 of 25 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 55 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 1346 tokens (~103/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
- Stability: 0.97 → pass security
- 20 Nov 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Analysed pypi/labmcp-sila2@0.1.2
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-sila2-v0.1.2 |
| Rekor log index | 2969518446 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4610965e4ffcbdb4ee863b27cd4af3388cb8d180a55721208e47d568563e2183 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 25 packages
| Packages resolved | 25 |
|---|---|
| Stale | 3 |
| 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 →
call_command Call Command ~178
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Command identifier |
| feature | string | yes | 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| done | boolean | yes | – |
| error | – | – | – |
| execution_id | – | – | For observable commands: use with get_command_status |
| feature | string | yes | – |
| observable | boolean | yes | – |
| progress | – | – | – |
| responses | – | – | – |
| status | – | – | – |
| timestamp | string | yes | – |
| warnings | array | yes | – |
No examples provided.
cancel_command Cancel Command ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| all_commands | boolean | – | Cancel every running command on the server |
| execution_id | – | – | Execution to cancel; omit (or all_commands=true) to cancel everything |
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | – | yes | – |
| message | string | yes | – |
| status_after | – | – | – |
| supported | boolean | yes | – |
| timestamp | string | yes | – |
No examples provided.
discover_servers Discover Servers ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_s | number | – | How long to listen for mDNS announcements |
| Name | Type | Req | Description |
|---|---|---|---|
| duration_s | number | yes | – |
| servers | array | yes | – |
| simulated | boolean | yes | – |
| timestamp | string | yes | – |
No examples provided.
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_command_result Get Command Result ~46
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.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| error | – | yes | – |
| execution_id | string | yes | – |
| feature | string | yes | – |
| responses | – | yes | – |
| status | string | yes | – |
| success | boolean | yes | – |
| timestamp | string | yes | – |
No examples provided.
get_command_status Get Command Status ~52
Status of an observable command started with `call_command`: waiting / running / finishedSuccessfully / finishedWithError, progress, estimated remaining time and the latest intermediate response.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| done | boolean | yes | – |
| estimated_remaining_s | – | yes | – |
| execution_id | string | yes | – |
| feature | string | yes | – |
| latest_intermediate_response | – | – | – |
| lifetime_of_execution_s | – | yes | How long the server keeps the result |
| parameters | – | yes | – |
| progress | – | yes | 0-1, if the server reports it |
| started | string | yes | – |
| status | string | yes | waiting, running, finishedSuccessfully or finishedWithError |
| timestamp | string | 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.
get_property Get Property ~81
Read the current value of a SiLA property (for observable properties: the first value of a subscription).
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | Feature identifier, e.g. 'TemperatureController' |
| metadata | – | – | SiLA client metadata, e.g. {'LockController.LockIdentifier': '...'} (if the server requires it) |
| property | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | – |
| observable | boolean | yes | – |
| property | string | yes | – |
| timestamp | string | yes | – |
| type | object | yes | JSON-schema-like description incl. unit (x-unit) and constraints |
| value | – | yes | – |
No examples provided.
get_server_info Get Server Info ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| cancellation_supported | boolean | yes | Server implements org.silastandard/core.commands/CancelController/v1 |
| command_allowlist | – | yes | Commands this bridge may call (None: all) |
| features | array | yes | Fully qualified identifiers of the implemented features |
| security | string | yes | – |
| server_description | – | – | – |
| server_name | – | – | – |
| server_type | – | – | – |
| server_uuid | – | – | – |
| server_version | – | – | – |
| simulated | boolean | yes | – |
| timestamp | string | yes | – |
| vendor_url | – | – | – |
No examples provided.
list_executions List Executions ~26
All observable command executions started in this session, newest last, with their status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_features List Features ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| features | array | yes | Per feature: commands (parameters/responses as JSON-schema-like dicts), properties, errors |
| 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.
subscribe_property Subscribe Property ~136
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).
| Name | Type | Req | Description |
|---|---|---|---|
| duration_s | number | – | How long to collect updates |
| feature | string | yes | 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | – |
| mode | string | yes | subscription (observable property) or polling |
| n_updates | integer | yes | – |
| property | string | yes | – |
| stats | – | yes | min/max/mean/first/last for numeric values |
| timestamp | string | yes | – |
| updates | array | yes | – |
No examples provided.
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.
pypi · labmcp-sila2
claude mcp add k-dense-ai-labmcp-sila2 -- uvx labmcp-sila2
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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 21 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 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.
What did VerifyMCP test on the SiLA 2 Bridge MCP server?
VerifyMCP ran 15 checks on SiLA 2 Bridge, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about SiLA 2 Bridge: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.