MCP.Market

LC-MS Worklist Builder MCP server

by K-Dense-AI·io.github.K-Dense-AI/labmcp-ms-worklist·v0.1.1·6 stars
No reviews yet

MCP server that builds and validates LC-MS worklists for MassLynx, SCIEX OS, MassHunter, Xcalibur.

A91/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

6 stars166 downloads/wk

Reviews

Write one

Nobody has reviewed LC-MS Worklist Builder yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

LC-MS Worklist Builder tools (9, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_samples

    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).

  • create_worklistwrite action

    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.

  • export_worklist

    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.

  • get_worklist

    Show a draft worklist in run order, with its defaults, blank/QC plan, randomisation seed and the history of operations applied to it.

  • import_worklist

    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.

  • insert_qc_blankswrite action

    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.

  • list_formats

    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.

  • list_worklists

    List the draft worklists in memory and the files in the output folder.

  • validate_worklist

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How LC-MS Worklist Builder compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
9
the typical server has 7
Tools that change things
22%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
6
more than 85% of 28,688 servers
Downloads a week
166
more than 72% of 12,191 servers with a package

What its tools let an agent do: 5 read · 4 create

Install LC-MS Worklist Builder in Claude Code, Cursor or VS Code

claude mcp add labmcp-ms-worklist -- uvx labmcp-ms-worklist
Add to Cursor

What the publisher says

From the LC-MS Worklist Builder repository's README, as published. We do not edit it. Read it on GitHub

LabMCP: Let AI Assistants Run Your Lab Instruments

<!-- COUNTS:START --> <!-- COUNTS:END -->

LabMCP lets an AI assistant such as Claude operate your laboratory instruments. You describe what you want in plain language, and the assistant weighs, heats, stirs, pumps, measures and logs for you. It stays inside safety limits you set, keeps a record of every command, and has a practice mode that needs no hardware.

It supports balances, hotplate stirrers, syringe pumps, spectrometers, mass spectrometers, potentiostats, lock-in amplifiers, temperature controllers, vacuum gauges, flow controllers, biosensors, clinical analyzers and more. You don't need to know how to program. Setup means installing one free helper program and pasting a few lines into your AI app's settings.

Free and open source, built by K-Dense.

You:        Tare the balance, then heat the stirrer to 60 °C at 400 rpm and log the pH every
            30 s until it's stable. Tell me when to add the reagent.

Assistant:  [tares the balance → sets stirring to 400 rpm → sets heating to 60 °C → logs pH …]
            "pH has been 7.41 ± 0.01 for 3 minutes. Ready for the reagent."

⭐ Help other scientists find this. If LabMCP is useful to you, please star the repo.

📋 Contents

  • How it works
  • Try it in 10 minutes (no instrument needed)
  • Supported instruments
  • Connect your real instrument
  • Safety
  • What every connector includes
  • Example requests
  • FAQ
  • Contributing
  • Roadmap

💡 How it works

You  ──type──▶  AI app  ──▶  LabMCP connector  ──USB / serial / network cable──▶  Instrument
                 (Claude,       (runs on the computer
                  Cursor, …)     attached to the instrument)
  • The AI app is where you type requests, e.g. Claude Desktop.
  • A LabMCP connector is a small program that knows one family of instruments and its command language, so the AI never has to guess it. You add one connector per type of instrument. (Technically these are MCP servers, which is the term you'll see in the tables and docs.)
  • MCP (Model Context Protocol) is the open standard that lets AI apps plug into tools like these. Think of it as USB for AI.
  • The AI can only use the actions a connector offers, like "tare", "set temperature" or "read pH". In the docs these actions are called tools. The connector checks every request against your limits and refuses anything unsafe before it reaches the instrument.

🚀 Try it in 10 minutes (no instrument needed)

Each connector has a practice mode (a simulator) that behaves like the real instrument and gives realistic replies. Nothing is connected, so nothing can go wrong.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

LC-MS Worklist Builder: common questions

Is LC-MS Worklist Builder MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the LC-MS Worklist Builder safety report
How do I install LC-MS Worklist Builder?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does LC-MS Worklist Builder need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is LC-MS Worklist Builder maintained?
The last commit was 38 days ago (2026-09-26). The latest release is v0.1.1.
How does LC-MS Worklist Builder compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 22% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from K-Dense-AI →