LC-MS Worklist Builder
PYPI · LABMCP-MS-WORKLIST · SCANNED SEP 30
MCP server that builds and validates LC-MS worklists for MassLynx, SCIEX OS, MassHunter, Xcalibur.
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 Security99
- No malware found by supply-chain analysis.Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1987 tokens (~165/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% 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 LC-MS Worklist Builder MCP server?
LC-MS Worklist Builder runs locally as a PyPI package, launched with uvx labmcp-ms-worklist. 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-ms-worklist
claude mcp add k-dense-ai-labmcp-ms-worklist -- uvx labmcp-ms-worklist
{
"mcpServers": {
"k-dense-ai-labmcp-ms-worklist": {
"command": "uvx",
"args": [
"labmcp-ms-worklist"
]
}
}
} {
"servers": {
"k-dense-ai-labmcp-ms-worklist": {
"command": "uvx",
"args": [
"labmcp-ms-worklist"
]
}
}
} codex mcp add k-dense-ai-labmcp-ms-worklist -- uvx labmcp-ms-worklist
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"k-dense-ai-labmcp-ms-worklist": {
"type": "local",
"command": [
"uvx",
"labmcp-ms-worklist"
],
"enabled": true
}
}
} openclaw mcp add k-dense-ai-labmcp-ms-worklist --command uvx --arg labmcp-ms-worklist
mcp_servers:
k-dense-ai-labmcp-ms-worklist:
command: "uvx"
args: ["labmcp-ms-worklist"] {
"McpServers": {
"k-dense-ai-labmcp-ms-worklist": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"labmcp-ms-worklist"
]
}
}
} assistant mcp add k-dense-ai-labmcp-ms-worklist -t stdio -c uvx -a labmcp-ms-worklist
{
"mcpServers": {
"k-dense-ai-labmcp-ms-worklist": {
"command": "uvx",
"args": [
"labmcp-ms-worklist"
]
}
}
} 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.
- 29 Sept 26 +10
- Provenance: unverified → pass ▲ security
- The attested source repository moved: K-Dense-AI/lab-instrument-mcps security
- 28 Sept 26 +31
- 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 −30
- 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.0 → 0.1.1 functional
- 26 Sept 26 69
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-ms-worklist@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-ms-worklist-v0.1.1 |
| Rekor log index | 2969517636 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:bf43492390407a9f360a454578d88ca3164140e6352509c0db82e2ff14714fc9 |
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 →
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 →
add_samples Add Samples ~79
Append samples to a draft worklist (the worklist's defaults and automatic positions apply; any blank/QC/randomisation plan is re-applied to the longer list with the same seed).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Draft worklist name |
| samples | array | yes | Samples in run order: objects (sample_name required) or plain sample names |
Structured output declared, but exposes no named fields.
No examples provided.
create_worklist Create Worklist ~420
Create an in-memory draft worklist from a sample list plus defaults (methods, injection volume, tray positions, data-file naming pattern). Nothing is written to disk until export_worklist. Injection volumes above the max_injection_volume_ul limit are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| bracket_type | integer | – | Xcalibur only: 1 Overlapped, 2 None, 3 Non-Overlapped, 4 Open |
| data_file_pattern | string | – | Data file naming pattern; placeholders {index} {sample_name} {sample_id} {type} {worklist} {date} {position}; illegal characters become '_' |
| data_path | string | – | Data folder (Xcalibur Path column) |
| first_position | string | – | If set, samples without a position get sequential positions from here, e.g. 'A1' |
| format | string | yes | Target vendor format (see list_formats) |
| injection_volume_ul | – | – | Injection volume in µL for samples that don't set one |
| lc_method | string | – | Default LC/inlet method (Waters INLET_FILE, SCIEX LC Method) |
| max_vial | integer | – | Highest vial number (vial_number pattern) |
| ms_method | string | – | Default MS/acquisition/instrument method |
| name | string | yes | Draft name (letters, digits, _ - .); used in file names |
| plate_size | integer | – | Positions per plate/tray |
| position_pattern | string | – | Autosampler position format to enforce |
| processing_method | string | – | Default processing method (SCIEX OS, Xcalibur) |
| replace | boolean | – | Replace an existing draft with the same name |
| samples | array | yes | Samples in run order: objects (sample_name required) or plain sample names |
| tune_file | string | – | Default tune file (Waters MS_TUNE_FILE) |
| vendor_columns | – | – | Constant vendor columns for every row, e.g. {'Rack Type': '...', 'Plate Type': '...'} |
Structured output declared, but exposes no named fields.
No examples provided.
export_worklist Export Worklist ~260
Validate the draft and write the vendor import file into the output folder. Returns the path, a preview of the first lines, warnings and import instructions. Refuses if validation finds errors or the file exists (unless overwrite=true). This does not start an acquisition: a person imports the file into the acquisition software.
| Name | Type | Req | Description |
|---|---|---|---|
| bracket_type | – | – | Xcalibur bracket type override |
| delimiter | – | – | Field separator (Xcalibur must match the Windows list separator) |
| filename | – | – | File name inside the output folder (default '<name>_<format>.csv') |
| format | – | – | Vendor format (default: the draft's); use another to convert |
| name | string | yes | Draft worklist name |
| overwrite | boolean | – | Replace an existing file of the same name |
| template_columns | – | – | Header columns to use instead of a template file |
| template_path | – | – | A blank batch/sequence/worklist exported from the vendor software, in the output folder; its header (and delimiter) is used |
| utf8_bom | – | – | Force a UTF-8 BOM on/off (default per format) |
| write_provenance | boolean | – | Also write <file>.provenance.json (history, seed, original sample order) |
Structured output declared, but exposes no named fields.
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_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_worklist Get Worklist ~59
Show a draft worklist in run order, with its defaults, blank/QC plan, randomisation seed and the history of operations applied to it.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | integer | – | – |
| name | string | yes | Draft worklist name |
Structured output declared, but exposes no named fields.
No examples provided.
import_worklist Import Worklist ~118
Parse an existing MassLynx, SCIEX OS, MassHunter or Xcalibur import file from the output folder into a draft, so it can be validated, edited or exported in another vendor's format. Columns without a neutral equivalent are kept verbatim. Only reads; nothing is written.
| Name | Type | Req | Description |
|---|---|---|---|
| format | – | – | Format; detected from the header if omitted |
| name | – | – | Draft name (default: the file name) |
| path | string | yes | File in the output folder (relative path) |
| replace | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
insert_qc_blanks Insert Qc Blanks ~319
Insert blanks and QC injections and optionally randomise the run order (with a recorded seed). Replaces any previous plan, so calling it again does not duplicate blanks. The plan is re-applied whenever samples are added; data-file names follow the new run order.
| Name | Type | Req | Description |
|---|---|---|---|
| blank_at_end | boolean | – | – |
| blank_at_start | boolean | – | – |
| blank_every_n | – | – | Insert a blank after every N samples |
| blank_injection_volume_ul | – | – | Injection volume in µL for samples that don't set one |
| blank_ms_method | string | – | Method for blanks (default: the worklist's ms_method) |
| blank_name | string | – | – |
| blank_position | string | – | Tray position of the blank vial |
| name | string | yes | Draft worklist name |
| qc_at_end | integer | – | Number of QC injections at the end |
| qc_at_start | integer | – | Number of QC injections at the start |
| qc_every_n | – | – | Insert a QC after every N samples |
| qc_injection_volume_ul | – | – | Injection volume in µL for samples that don't set one |
| qc_name | string | – | – |
| qc_position | string | – | Tray position of the pooled QC vial |
| randomize | boolean | – | Randomise the run order of the samples first |
| randomize_types | array | – | Which sample types are shuffled among their own slots (standards stay put by default) |
| seed | – | – | Random seed (a new one is drawn and recorded if omitted) |
Structured output declared, but exposes no named fields.
No examples provided.
list_formats List Formats ~86
List the supported import formats (Waters MassLynx, SCIEX OS, Agilent MassHunter, Thermo Xcalibur): columns, required fields, sample-type names, file extensions, how to import, what is verified against vendor documents and what is assumed, and the source URLs. Also lists the position patterns and the formats that were researched but not implemented.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_worklists List Worklists ~24
List the draft worklists in memory and the files in the output folder.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
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.
validate_worklist Validate Worklist ~98
Check a draft against the target format: required fields, duplicate data-file names, characters Windows does not allow in file names, tray/vial position format and plate bounds, injection volume (> 0 and <= the max_injection_volume_ul limit), and method file extensions. Errors block export; warnings don't.
| Name | Type | Req | Description |
|---|---|---|---|
| format | – | – | Validate for another vendor format (default: the draft's) |
| name | string | yes | Draft worklist name |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| format | string | yes | – |
| sample_count | integer | yes | – |
| valid | boolean | yes | True when there are no errors (warnings are allowed) |
| warnings | array | yes | – |
| worklist | string | yes | – |
No examples provided.
What is the LC-MS Worklist Builder MCP server?
LC-MS Worklist Builder is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-ms-worklist. MCP server that builds and validates LC-MS worklists for MassLynx, SCIEX OS, MassHunter, Xcalibur. This page covers its PyPI package (labmcp-ms-worklist).
Is the LC-MS Worklist Builder MCP server safe to use?
LC-MS Worklist Builder scores 81 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 LC-MS Worklist Builder MCP server expose?
LC-MS Worklist Builder exposes 12 tools: get_connection_info, get_command_log, reconnect, list_formats, create_worklist, and 7 more. Their descriptions and schemas cost roughly 1,584 tokens of context every time the server is loaded.
Is the LC-MS Worklist Builder MCP server still maintained?
LC-MS Worklist Builder 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 LC-MS Worklist Builder MCP server under?
LC-MS Worklist Builder 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.