Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ocean Insight Spectrometer

PYPI · LABMCP-OCEAN-SPECTROMETER

MCP server for Ocean Insight / Ocean Optics spectrometers (python-seabreeze).

−15 this week 80 Trust /100

Last scanned (20 hours ago)

Scores higher than 78% of PyPI servers

Category Health and Science

Trust breakdown (7 categories)

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 55 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2108 tokens (~131/item across 16 items; 16 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
What we tested

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 →

Changelog

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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-ocean-spectrometer@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-ocean-spectrometer-v0.1.2
Rekor log index 2969517732
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b6d6bc4d4303aa1b7f60a634ce73a06eca832da8e58cd70a7175a4d1625b0aaf

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 19 packages
Packages resolved 19
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~1,658 tokens

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 →

Tool Tokens
acquire_spectrum ~260

Acquire an intensity spectrum (raw counts) with optional averaging, boxcar smoothing and corrections. Returns downsampled (wavelength, counts), summary statistics, the most prominent peaks with FWHM, and a saturation check; `save_path` writes the full spectrum to a new .csv file (an existing file is never overwritten).

NameTypeReqDescription
boxcar_half_widthinteger–Boxcar smoothing: pixels averaged on EACH side (0 = off)
correct_dark_countsboolean–Subtract the mean of the optically masked (electric dark) pixels
correct_nonlinearityboolean–Apply the EEPROM nonlinearity correction
max_pointsinteger–Maximum points returned (bin-averaged)
num_peaksinteger–Number of peaks to report
save_path––Optional new .csv file for the full-resolution data (existing files are not overwritten)
scans_to_averageinteger–Spectra averaged together
subtract_stored_darkboolean–Subtract the stored dark spectrum (same settings required)
wavelength_max_nm––Only report/search below this wavelength (nm)
wavelength_min_nm––Only report/search above this wavelength (nm)
NameTypeReqDescription
boxcar_half_widthintegeryes–
correct_dark_countsbooleanyes–
correct_nonlinearitybooleanyes–
dark_subtractedbooleanyes–
integration_time_msnumberyes–
intensity_countsarrayyesBin-averaged counts (downsampled)
max_at_nmnumberyes–
max_countsnumberyes–
mean_countsnumberyes–
min_countsnumberyes–
modelstringyes–
peak_raw_percent_of_saturationnumberyesHighest raw count in any scan, % of saturation
peaksarrayyesMost prominent peaks, found on the full-resolution spectrum
pixelsintegeryes–
points_returnedintegeryes–
saturatedbooleanyes–
saturated_pixelsintegeryes–
saturation_countsnumberyes–
saved_to–yes–
scans_to_averageintegeryes–
serialstringyes–
timestampstringyes–
warningsarrayyes–
wavelength_nmarrayyesBin-averaged wavelengths (downsampled to max_points)

No examples provided.

auto_integration_time ~148

Adjust the integration time until the brightest raw pixel (optionally within a wavelength window) is within the target band of saturation (default 70-85 %). Stays within the device limits and the `max_integration_time_ms` safety limit. Re-take dark/reference afterwards.

NameTypeReqDescription
max_iterationsinteger–Maximum adjustment steps
target_max_percentnumber–Upper edge of the target band, % of saturation
target_min_percentnumber–Lower edge of the target band, % of saturation
wavelength_max_nm––Only report/search below this wavelength (nm)
wavelength_min_nm––Only report/search above this wavelength (nm)

Structured output declared, but exposes no named fields.

No examples provided.

detector_cooling_off ~35

Switch the detector thermo-electric cooler off (the detector warms to ambient). Does nothing on spectrometers without a TEC.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

find_peaks ~152

Find peaks (or dips) with position, height, prominence and FWHM in the most recent spectrum (intensity, absorbance or transmittance). Acquires a fresh intensity spectrum if none has been taken yet.

NameTypeReqDescription
max_peaksinteger–Maximum number of peaks
min_prominence_fractionnumber–Minimum prominence as a fraction of the data range
min_separation_nmnumber–Minimum distance between peaks, nm
modestring–Peaks (maxima) or dips (minima)
wavelength_max_nm––Only report/search below this wavelength (nm)
wavelength_min_nm––Only report/search above this wavelength (nm)

Structured output declared, but exposes no named fields.

No examples provided.

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.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

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_device_info ~40

Model, serial, pixel count, wavelength range, integration-time limits, saturation level, supported corrections, TEC presence, and which dark/reference spectra are stored.

Input schema present but exposes no named parameters.

NameTypeReqDescription
backendstringyes–
dark_stored–yesTimestamp of the stored dark, if any
electric_dark_correctionbooleanyes–
has_tecbooleanyes–
integration_time_max_msnumberyes–
integration_time_min_msnumberyes–
integration_time_msnumberyes–
modelstringyes–
nonlinearity_correctionbooleanyes–
pixelsintegeryes–
reference_stored–yesTimestamp of the stored reference, if any
saturation_countsnumberyesmax_intensity: raw counts at full scale
serialstringyes–
wavelength_max_nmnumberyes–
wavelength_min_nmnumberyes–

No examples provided.

list_spectrometers ~53

List the Ocean spectrometers seabreeze can see (model, serial number, whether open) and which one this server is connected to. Use a serial number as `--address` to pick one.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

measure_absorbance ~195

Measure the absorbance spectrum A = -log10((S - D) / (R - D)) of the sample now in the beam, using the stored dark D and reference R (same settings). Ask the user to insert the sample first. Also returns values at `wavelengths_nm` and the absorbance maxima.

NameTypeReqDescription
max_pointsinteger–Maximum points returned (bin-averaged)
num_peaksinteger–Number of peaks to report
save_path––Optional new .csv file for the full-resolution data (existing files are not overwritten)
scans_to_average––Spectra averaged (default: as the reference)
wavelength_max_nm––Only report/search below this wavelength (nm)
wavelength_min_nm––Only report/search above this wavelength (nm)
wavelengths_nm––Wavelengths (nm) at which to report interpolated values
NameTypeReqDescription
at_wavelengthsarrayyes–
dark_timestampstringyes–
integration_time_msnumberyes–
kindstringyes–
max_at_nm–yes–
max_value–yes–
peaksarrayyesAbsorbance maxima, or transmittance minima (dips)
pixelsintegeryes–
points_returnedintegeryes–
reference_timestampstringyes–
saved_to–yes–
scans_to_averageintegeryes–
timestampstringyes–
unitsstringyesAU (absorbance, -log10 T) or % (transmittance)
valid_pixelsintegeryesPixels where the reference had enough unsaturated signal
valuesarrayyesDownsampled values; None where invalid
warningsarrayyes–
wavelength_nmarrayyes–

No examples provided.

measure_transmittance ~191

Measure the transmittance spectrum %T = 100 (S - D) / (R - D) of the sample now in the beam, using the stored dark and reference. Ask the user to insert the sample first. Also returns values at `wavelengths_nm` and the deepest transmission dips.

NameTypeReqDescription
max_pointsinteger–Maximum points returned (bin-averaged)
num_peaksinteger–Number of peaks to report
save_path––Optional new .csv file for the full-resolution data (existing files are not overwritten)
scans_to_average––Spectra averaged (default: as the reference)
wavelength_max_nm––Only report/search below this wavelength (nm)
wavelength_min_nm––Only report/search above this wavelength (nm)
wavelengths_nm––Wavelengths (nm) at which to report interpolated values
NameTypeReqDescription
at_wavelengthsarrayyes–
dark_timestampstringyes–
integration_time_msnumberyes–
kindstringyes–
max_at_nm–yes–
max_value–yes–
peaksarrayyesAbsorbance maxima, or transmittance minima (dips)
pixelsintegeryes–
points_returnedintegeryes–
reference_timestampstringyes–
saved_to–yes–
scans_to_averageintegeryes–
timestampstringyes–
unitsstringyesAU (absorbance, -log10 T) or % (transmittance)
valid_pixelsintegeryesPixels where the reference had enough unsaturated signal
valuesarrayyesDownsampled values; None where invalid
warningsarrayyes–
wavelength_nmarrayyes–

No examples provided.

read_detector_temperature ~42

Read the detector temperature from the thermo-electric cooler (TE-cooled models such as the QE Pro, when seabreeze exposes the thermo_electric feature for them).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

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.

set_detector_cooling ~97

Enable the detector thermo-electric cooler at `setpoint_c` (TE-cooled models only). The detector takes minutes to settle; dark current (and noise) drops as it cools. The TEC can only cool to roughly 15-40 °C below ambient (QE Pro manual). Checked against `min_tec_setpoint_c`.

NameTypeReqDescription
setpoint_cnumberyesDetector TEC setpoint, °C

Structured output declared, but exposes no named fields.

No examples provided.

set_integration_time ~57

Set the detector integration time (ms), within the device limits from `get_device_info`. Stored dark/reference spectra become unusable until re-taken at the new time.

NameTypeReqDescription
integration_time_msnumberyesIntegration time in ms

Structured output declared, but exposes no named fields.

No examples provided.

store_dark_reference ~138

Record and store a DARK spectrum (kept in memory) for absorbance/transmittance. BEFORE calling, ask the user to BLOCK THE LIGHT PATH (close the shutter, switch the lamp off or cap the fiber) and wait for confirmation. Uses the present integration time.

NameTypeReqDescription
boxcar_half_widthinteger–Boxcar smoothing: pixels averaged on EACH side (0 = off)
correct_dark_countsboolean–Electric-dark correction (use the same later)
correct_nonlinearityboolean–Nonlinearity correction (use the same later)
scans_to_averageinteger–Spectra averaged together
NameTypeReqDescription
boxcar_half_widthintegeryes–
correct_dark_countsbooleanyes–
correct_nonlinearitybooleanyes–
integration_time_msnumberyes–
kindstringyes–
max_at_nmnumberyes–
max_countsnumberyes–
mean_countsnumberyes–
peak_raw_percent_of_saturationnumberyes–
saturated_pixelsintegeryes–
scans_to_averageintegeryes–
timestampstringyes–
warningsarrayyes–

No examples provided.

store_reference ~129

Record and store the REFERENCE (100 % transmission) spectrum in memory. BEFORE calling, ask the user to put the BLANK (solvent-filled or empty cuvette) in the beam with the light on, and wait for confirmation. Use the same settings as the dark.

NameTypeReqDescription
boxcar_half_widthinteger–Boxcar smoothing: pixels averaged on EACH side (0 = off)
correct_dark_countsboolean–Must match the stored dark
correct_nonlinearityboolean–Must match the stored dark
scans_to_averageinteger–Spectra averaged together
NameTypeReqDescription
boxcar_half_widthintegeryes–
correct_dark_countsbooleanyes–
correct_nonlinearitybooleanyes–
integration_time_msnumberyes–
kindstringyes–
max_at_nmnumberyes–
max_countsnumberyes–
mean_countsnumberyes–
peak_raw_percent_of_saturationnumberyes–
saturated_pixelsintegeryes–
scans_to_averageintegeryes–
timestampstringyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Ocean Insight Spectrometer MCP server?

Ocean Insight Spectrometer runs locally as a PyPI package, launched with uvx labmcp-ocean-spectrometer. 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-ocean-spectrometer

# add to Claude Code
claude mcp add k-dense-ai-labmcp-ocean-spectrometer -- uvx labmcp-ocean-spectrometer
Common questions

What is the Ocean Insight Spectrometer MCP server?

Ocean Insight Spectrometer is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-ocean-spectrometer. MCP server for Ocean Insight / Ocean Optics spectrometers (python-seabreeze). This page covers its PyPI package (labmcp-ocean-spectrometer).

Is the Ocean Insight Spectrometer MCP server safe to use?

Ocean Insight Spectrometer scores 80 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 Ocean Insight Spectrometer MCP server expose?

Ocean Insight Spectrometer exposes 16 tools: get_connection_info, get_command_log, reconnect, list_spectrometers, get_device_info, and 11 more. Their descriptions and schemas cost roughly 1,658 tokens of context every time the server is loaded.

Is the Ocean Insight Spectrometer MCP server still maintained?

Ocean Insight Spectrometer 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 Ocean Insight Spectrometer MCP server under?

Ocean Insight Spectrometer 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 Ocean Insight Spectrometer MCP server?

VerifyMCP ran 15 checks on Ocean Insight Spectrometer, 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 Ocean Insight Spectrometer: 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.