Skip to main content
Glama
thermophysical-curator

thermophysical-curator

by frankmtetwa

Thermophysical Data Curation MCP Server

An MCP server for auditable thermophysical data curation using five supplied JR-MPNN checkpoints and selected UManSysProp group-contribution methods.

What it provides

  • inspect_molecule: validate and canonicalize a SMILES string and report domain flags.

  • predict_jrmpnn: predict Tm, Tb, Tc, Pc, and Vc with Joback baselines.

  • assess_jrmpnn_training_similarity: compare a query with the 10 nearest property-specific JR-MPNN training embeddings without returning private records.

  • estimate_umansysprop: estimate boiling point, critical properties, density, and vapor pressure.

  • curate_thermophysical_records: normalize, deduplicate, score, and triage records with an audit trail.

  • server_capabilities: report available models, methods, and scientific limitations.

Predictions are diagnostic cross-checks. They do not replace accepted experimental measurements, and the server never silently deletes submitted records.

Related MCP server: GNNPCSAFT MCP Server

Install from source

Python 3.11 or newer is required. Installation may take several minutes because PyTorch, PyTorch Geometric, RDKit, and the scientific dependencies are substantial.

git clone https://github.com/frankmtetwa/thermophysical-curator.git
cd thermophysical-curator
python -m venv .venv

Activate the environment:

# Windows PowerShell
.\.venv\Scripts\Activate.ps1
# macOS/Linux
source .venv/bin/activate

Then install and test:

python -m pip install --upgrade pip
python -m pip install .
python -m unittest discover -s tests -v

Run the stdio MCP server with:

thermophysical-curator

The process waits for an MCP client on standard input. That behavior is expected.

Enable training-similarity assessment

The repository does not contain proprietary training compounds or generated embedding indices. On each computer where similarity assessment is required, create a private reference directory containing these five files:

private_reference/
|-- Tm_train_smiles.csv
|-- Tb_train_smiles.csv
|-- Tc_train_smiles.csv
|-- Pc_train_smiles.csv
`-- Vc_train_smiles.csv

Each CSV must contain a smiles column. A compound_id column is optional:

compound_id,smiles

Privacy-safe header-only examples are available in reference_templates/. Copy them to private_reference/, then populate them locally with the SMILES used to train the corresponding property model. Do not combine calibration or test compounds with the training set.

Build the private embedding indices after installing the project:

python -m curation_agent.similarity build

The default location is private_reference/ in the repository root. To keep the files elsewhere, set THERMOPHYSICAL_REFERENCE_DIR to an absolute directory before building the indices and before launching the MCP server. Restart the MCP client after building so it refreshes the available tool state.

The reported training-similarity percentile is an applicability-domain diagnostic, not a calibrated uncertainty interval or a guarantee of prediction accuracy.

Claude Desktop

MCPB extension

This repository contains an experimental cross-platform UV manifest. Install the MCPB CLI and build the extension from the repository root:

npm install -g @anthropic-ai/mcpb
mcpb validate manifest.json
mcpb pack . dist/thermophysical-curator-0.1.0.mcpb

In Claude Desktop, open Settings > Extensions > Advanced settings > Install Extension and select the generated .mcpb file. The UV runtime downloads the Python dependencies on first launch, so the initial startup can be slow. When Claude asks for the Private JR-MPNN reference directory, select the private_reference directory containing both the five CSV files and the generated embeddings/ directory. The private files remain outside the extension bundle.

Manual configuration

Users who prefer a pre-created virtual environment can add this to Claude Desktop's MCP configuration, replacing the command with the absolute path to their environment:

{
  "mcpServers": {
    "thermophysical-curator": {
      "command": "C:\\path\\to\\repo\\.venv\\Scripts\\python.exe",
      "args": ["-m", "curation_agent.server"]
    }
  }
}

On macOS/Linux, use /path/to/repo/.venv/bin/python instead.

Codex

After installing the project, register the server using the environment's Python:

codex mcp add thermophysical-curator -- /absolute/path/to/python -m curation_agent.server

Example curation record

{
  "smiles": "CCO",
  "property": "normal_boiling_point",
  "value": 78.37,
  "unit": "C",
  "source": "literature citation",
  "doi": "10.xxxx/example",
  "experimental": true,
  "method": "ebulliometry",
  "uncertainty": 0.1
}

Privacy

The package contains model weights but no training, calibration, or proprietary experimental records. Inputs are processed locally by the MCP server. The host AI application may still receive tool arguments and results, subject to that application's privacy policy.

Redistribution checklist

Before making the repository public, verify that you have permission to redistribute the five JR-MPNN .pth checkpoint files. They are required for model predictions but their redistribution terms were not present in the supplied source directory.

UManSysProp-derived files retain their original copyright notices and GPL terms. See THIRD_PARTY_NOTICES.md and LICENSE.

License

GPL-3.0-or-later, subject to the third-party notices and checkpoint redistribution rights described above.

Available Tools

6 tools
assess_jrmpnn_training_similarityB

Assess similarity to a property's private JR-MPNN training embeddings.

Uses mean Euclidean distance to the 10 nearest graph embeddings. Private Training SMILES, embeddings, and reference identifiers are never returned.

Inputs: smiles (required), property_name (required). Returns: object

curate_thermophysical_recordsA

Normalize, deduplicate, score, and triage records with a full audit trail.

Each record should contain smiles, property, value, and unit. Strongly recommended provenance fields are source or doi, experimental, method, and uncertainty. The tool never silently removes a record.

Inputs: records (required), model_check, relative_deviation_threshold. Returns: object

estimate_umansyspropC

Run UManSysProp group-contribution estimates without its legacy web UI.

Inputs: smiles (required), temperature_k, critical_method, boiling_point_method. Returns: object

inspect_moleculeC

Validate and canonicalize a SMILES string and report model-domain flags.

Inputs: smiles (required). Returns: object

predict_jrmpnnB

Predict Tm, Tb, Tc, Pc, and/or Vc with the supplied JR-MPNN checkpoints.

Property symbols are Tm, Tb, Tc, Pc, and Vc. Returned intervals are clearly marked as uncalibrated because the paper's k-NN calibration artifacts are not present in this workspace.

Inputs: smiles (required), properties. Returns: object

server_capabilitiesB

Describe supported properties, methods, and important scientific limits.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: SMILES validation, JR-MPNN prediction, training-similarity/applicability-domain assessment, UManSysProp estimation, record curation, and a capabilities meta-tool. The two property-prediction tools (predict_jrmpnn and estimate_umansysprop) overlap in output but are clearly separated by method, so mild confusion is possible but descriptions resolve it.

    Naming Consistency4/5

    Names are uniformly snake_case with clear verb_noun structure (inspect_molecule, predict_jrmpnn, assess_jrmpnn_training_similarity, estimate_umansysprop, curate_thermophysical_records). The lone noun-only server_capabilities is a minor deviation from the verb-led pattern.

    Tool Count5/5

    Six tools is well-scoped for a thermophysical prediction-and-curation server, with each tool covering a coherent responsibility. No tool feels redundant or missing at the count level.

    Completeness4/5

    The surface covers the core lifecycle: molecule validation, two prediction paths, applicability-domain assessment, curation with audit trail, and a capabilities descriptor. Batch prediction/curation or result-export operations are not exposed, but the primary workflows are covered without obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers