# ASTM LIS Analyzer Receiver (pypi · labmcp-astm-lis)

MCP server that receives results from clinical/lab analyzers over ASTM E1381/E1394 (CLSI LIS1/LIS2).

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- pypi · `labmcp-astm-lis`: 83/100 (this document), [markdown](https://verifymcp.io/servers/k-dense-ai-labmcp-astm-lis/labmcp-astm-lis.md), [page](https://verifymcp.io/servers/k-dense-ai-labmcp-astm-lis/labmcp-astm-lis)

## Channel facts

- Registry: `pypi`
- Package: `labmcp-astm-lis`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-30.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 2 of 17 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K-Dense-AI/lab-instrument-mcps).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1020 tokens (~127/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ASTM LIS Analyzer Receiver MCP server?

ASTM LIS Analyzer Receiver runs locally as a PyPI package, launched with uvx labmcp-astm-lis. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add k-dense-ai-labmcp-astm-lis -- uvx labmcp-astm-lis
```

### Cursor

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-astm-lis": {
      "command": "uvx",
      "args": [
        "labmcp-astm-lis"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k-dense-ai-labmcp-astm-lis": {
      "command": "uvx",
      "args": [
        "labmcp-astm-lis"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k-dense-ai-labmcp-astm-lis -- uvx labmcp-astm-lis
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k-dense-ai-labmcp-astm-lis": {
      "type": "local",
      "command": [
        "uvx",
        "labmcp-astm-lis"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k-dense-ai-labmcp-astm-lis --command uvx --arg labmcp-astm-lis
```

### Hermes

```yaml
mcp_servers:
  k-dense-ai-labmcp-astm-lis:
    command: "uvx"
    args: ["labmcp-astm-lis"]
```

### Netclaw

```json
{
  "McpServers": {
    "k-dense-ai-labmcp-astm-lis": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "labmcp-astm-lis"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k-dense-ai-labmcp-astm-lis -t stdio -c uvx -a labmcp-astm-lis
```

### Other

```json
{
  "mcpServers": {
    "k-dense-ai-labmcp-astm-lis": {
      "command": "uvx",
      "args": [
        "labmcp-astm-lis"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-30 (score 83, +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.

### 2026-09-29 (score 82, +10)

- [security improvement] Provenance: unverified → pass
- [security] The attested source repository moved: K-Dense-AI/lab-instrument-mcps

### 2026-09-28 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.2 → 0.1.3

### 2026-09-26 (score 71)

First indexed and scored.

## MCP tools (8)

### `get_connection_info` (~40 tokens)

Get Connection Info

Report which instrument is connected (identity, address, simulated or real),
whether the server is read-only, and the active safety limits. Call this first.

### `get_command_log` (~46 tokens)

Get Command Log

Return the most recent raw commands sent to / replies received from the
instrument (newest last). Useful for debugging and for recording what was done.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (array)

### `reconnect` (~35 tokens)

Reconnect

Close and re-open the connection to the instrument (e.g. after it was power
cycled or a cable was re-plugged).

### `get_connection_status` (~67 tokens)

Get Connection Status

Report the analyzer link state, the messages and results received, and link-layer error
counters.

Shows the link (serial / TCP client / TCP listener), whether an analyzer is connected, whether
a transmission is in progress, and NAKed frames, checksum errors and retransmissions.

Output parameters:

- `address` (string)
- `allow_from`
- `last_activity_at`
- `last_analyzer`
- `last_error`
- `last_message_at`
- `last_store_error`
- `link` (object)
- `link_state` (string)
- `messages` (integer)
- `mode` (string): serial, tcp-client, tcp-listen or simulated
- `receiver_running` (boolean)
- `redact_patient_info` (boolean)
- `rejected_connections`
- `results` (integer)
- `session_state` (string): receiving (inside ENQ ... EOT) or idle
- `started_at` (string)
- `store_path`
- `store_write_errors` (integer): Messages that could not be appended to store_path (kept in memory)

### `list_received_messages` (~82 tokens)

List Received Messages

List the most recent ASTM messages received (newest last).

Each entry shows the analyzer, number of records and results, sample IDs, whether the
message was complete, and any parser warnings.

Input parameters:

- `limit` (integer): Most recent messages to return
- `since`: Only messages received at/after this ISO 8601 time (UTC if no zone)

Output parameters:

- `messages` (array)
- `returned` (integer)
- `total` (integer)

### `get_results` (~170 tokens)

Get Results

Return received results, filtered by sample ID, patient ID, test code, time received or
abnormal flag (newest last).

Each result has its value exactly as transmitted, units, reference range, flags, status and
any comment records that followed it.

Input parameters:

- `abnormal_only` (boolean): Only results with an abnormal flag other than N
- `limit` (integer): Most recent matching results to return
- `patient_id`: Patient ID as sent by the analyzer (exact match)
- `sample_id`: Sample / specimen ID (case-insensitive exact match)
- `since`: Only results received at/after this ISO 8601 time (UTC if no zone)
- `test_code`: Analyzer test code, e.g. WBC, GLU, TSH (case-insensitive)

Output parameters:

- `redacted` (boolean)
- `results` (array)
- `returned` (integer)
- `total_matches` (integer)
- `truncated` (boolean)

### `get_result_detail` (~84 tokens)

Get Result Detail

Show every decoded field of one result, with its comments, order and patient context, raw
records and message header.

Includes universal test ID components, operator, start/completion times, instrument,
priority and specimen type. Patient identifiers stay redacted unless disabled at launch.

Input parameters:

- `result_id` (string, required): result_id from get_results, e.g. '3-12'

Output parameters:

- `message` (object): Header information of the message the result came in
- `redacted_fields` (array)
- `result` (object)

### `clear_results` (~43 tokens)

Clear Results

Delete all received messages and results from this server's memory (e.g. between runs).

The optional JSONL store file is not modified. Nothing is sent to the analyzer.

Output parameters:

- `cleared_messages` (integer)
- `cleared_results` (integer)
- `note` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k-dense-ai-labmcp-astm-lis/labmcp-astm-lis#diagnostics

## Score history

- 2026-09-30: 83
- 2026-09-29: 82
- 2026-09-28: 72
- 2026-09-27: 71
- 2026-09-26: 71

## Common questions

### What is the ASTM LIS Analyzer Receiver MCP server?

ASTM LIS Analyzer Receiver is an MCP server listed in the public MCP registry as io.github.K-Dense-AI/labmcp-astm-lis. MCP server that receives results from clinical/lab analyzers over ASTM E1381/E1394 (CLSI LIS1/LIS2). This page covers its PyPI package (labmcp-astm-lis).

### Is the ASTM LIS Analyzer Receiver MCP server safe to use?

ASTM LIS Analyzer Receiver scores 83 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 ASTM LIS Analyzer Receiver MCP server expose?

ASTM LIS Analyzer Receiver exposes 8 tools: get_connection_info, get_command_log, reconnect, get_connection_status, list_received_messages, and 3 more. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.

### Is the ASTM LIS Analyzer Receiver MCP server still maintained?

ASTM LIS Analyzer Receiver 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 ASTM LIS Analyzer Receiver MCP server under?

ASTM LIS Analyzer Receiver 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.

## Links

- PyPI project: https://pypi.org/project/labmcp-astm-lis/
- Socket report: https://socket.dev/pypi/package/labmcp-astm-lis
- Repository: https://github.com/K-Dense-AI/lab-instrument-mcps
- Website: https://github.com/K-Dense-AI/lab-instrument-mcps/tree/main/servers/health/astm-lis-analyzer
- Changelog RSS feed: https://verifymcp.io/servers/k-dense-ai-labmcp-astm-lis/labmcp-astm-lis.xml
- Changelog JSON feed: https://verifymcp.io/servers/k-dense-ai-labmcp-astm-lis/labmcp-astm-lis.json
- HTML version of this page: https://verifymcp.io/servers/k-dense-ai-labmcp-astm-lis/labmcp-astm-lis