Labmate MCP Server

labmate-mcp PyPI v7.3.1

Published by jonasrackl — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Your AI lab companion — 78 MCP tools from literature search to benchwork to publication

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 81

Each tool and what it can reach — statically extracted from the published source.

  • search_web_of_scienceingests untrusted input
  • analyze_research_topicno sensitive capability
  • assign_peptide_ms_peaksno sensitive capability
  • build_bibliographyno sensitive capability
  • calculate_buffer_phno sensitive capability
  • calculate_concentrationno sensitive capability
  • calculate_dilutionno sensitive capability
  • calculate_isotope_patternno sensitive capability
  • calculate_molarityno sensitive capability
  • calculate_peptide_extinctionno sensitive capability
Show 71 more tools ↓
  • calculate_peptide_pino sensitive capability
  • calculate_reaction_massno sensitive capability
  • calculate_yieldno sensitive capability
  • check_peptide_synthesisno sensitive capability
  • classify_natural_productno sensitive capability
  • compute_descriptorsno sensitive capability
  • convert_unitsno sensitive capability
  • find_open_access_pdfno sensitive capability
  • find_similar_papersno sensitive capability
  • format_citationno sensitive capability
  • format_molecular_formulano sensitive capability
  • generate_bibtexno sensitive capability
  • generate_peptide_libraryno sensitive capability
  • generate_si_checklistno sensitive capability
  • get_author_profileno sensitive capability
  • get_chemrxiv_categoriesno sensitive capability
  • get_compound_propertiesno sensitive capability
  • get_journal_metricsno sensitive capability
  • get_paper_citationsno sensitive capability
  • get_paper_detailsno sensitive capability
  • get_paper_referencesno sensitive capability
  • get_peptide_ion_seriesno sensitive capability
  • get_protein_structureno sensitive capability
  • get_safety_datano sensitive capability
  • get_thesis_guideno sensitive capability
  • lookup_abbreviationno sensitive capability
  • lookup_amino_acid_propertiesno sensitive capability
  • lookup_buffer_recipeno sensitive capability
  • lookup_column_chromatographyno sensitive capability
  • lookup_cooling_bathno sensitive capability
  • lookup_experimental_templateno sensitive capability
  • lookup_iupac_nameno sensitive capability
  • lookup_journal_guideno sensitive capability
  • lookup_lab_tipsno sensitive capability
  • lookup_named_reactionno sensitive capability
  • lookup_nmr_solventno sensitive capability
  • lookup_periodic_tableno sensitive capability
  • lookup_protecting_groupno sensitive capability
  • lookup_rxn_dev_checklistno sensitive capability
  • lookup_safety_cardno sensitive capability
  • lookup_solvent_propertiesno sensitive capability
  • lookup_tlc_stainno sensitive capability
  • lookup_workup_procedureno sensitive capability
  • modify_peptideno sensitive capability
  • name_to_smilesno sensitive capability
  • peptide_cyclization_optionsno sensitive capability
  • peptide_propertiesno sensitive capability
  • peptide_to_smilesno sensitive capability
  • plan_synthesisno sensitive capability
  • predict_admetno sensitive capability
  • predict_atom_mappingno sensitive capability
  • predict_nmrno sensitive capability
  • predict_pkano sensitive capability
  • predict_productno sensitive capability
  • predict_retrosynthesisno sensitive capability
  • predict_solubilityno sensitive capability
  • profile_compoundno sensitive capability
  • search_binding_datano sensitive capability
  • search_chemrxivno sensitive capability
  • search_compoundno sensitive capability
  • search_crystal_structuresno sensitive capability
  • search_mass_spectrano sensitive capability
  • search_materials_projectno sensitive capability
  • search_nist_webbookno sensitive capability
  • search_papersno sensitive capability
  • search_protein_structuresno sensitive capability
  • search_tautomersno sensitive capability
  • search_toxicityno sensitive capability
  • text_to_procedureno sensitive capability
  • translate_compound_idsno sensitive capability
  • validate_cas_numberno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v7.3.1 latest A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/labmate-mcp/badge.svg)](https://mcptrustchecker.com/registry/labmate-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/labmate-mcp"><img src="https://mcptrustchecker.com/registry/labmate-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/labmate-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan labmate-mcp --online --registry pypi

Use the free API → How scoring works

More in Learning & Documentation