ASTM LIS Analyzer Receiver
PYPI · LABMCP-ASTM-LIS
MCP server that receives results from clinical/lab analyzers over ASTM E1381/E1394 (CLSI LIS1/LIS2).
Available components
Last scanned (10 hours ago)
Scores higher than 78% of PyPI servers
Category Health and Science
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 17 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
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 →
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.
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Nov 26 +15
- Malware scan: unverified → pass ▲ 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 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.90 functional
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-astm-lis@0.1.3
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-astm-lis-v0.1.3 |
| Rekor log index | 2969518000 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:656e21c0f387fc8ecb0a4b9b89c10d0cd3205fa5f5b094378c23bbf2c68b1b18 |
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 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
clear_results Clear Results ~43
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cleared_messages | integer | yes | – |
| cleared_results | integer | yes | – |
| note | string | yes | – |
No examples provided.
get_command_log 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_connection_info 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_connection_status Get Connection Status ~67
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| allow_from | – | – | – |
| last_activity_at | – | yes | – |
| last_analyzer | – | yes | – |
| last_error | – | yes | – |
| last_message_at | – | yes | – |
| last_store_error | – | – | – |
| link | object | yes | – |
| link_state | string | yes | – |
| messages | integer | yes | – |
| mode | string | yes | serial, tcp-client, tcp-listen or simulated |
| receiver_running | boolean | yes | – |
| redact_patient_info | boolean | yes | – |
| rejected_connections | – | – | – |
| results | integer | yes | – |
| session_state | string | yes | receiving (inside ENQ ... EOT) or idle |
| started_at | string | yes | – |
| store_path | – | yes | – |
| store_write_errors | integer | – | Messages that could not be appended to store_path (kept in memory) |
No examples provided.
get_result_detail Get Result Detail ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| result_id | string | yes | result_id from get_results, e.g. '3-12' |
| Name | Type | Req | Description |
|---|---|---|---|
| message | object | yes | Header information of the message the result came in |
| redacted_fields | array | yes | – |
| result | object | yes | – |
No examples provided.
get_results Get Results ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| redacted | boolean | yes | – |
| results | array | yes | – |
| returned | integer | yes | – |
| total_matches | integer | yes | – |
| truncated | boolean | yes | – |
No examples provided.
list_received_messages List Received Messages ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most recent messages to return |
| since | – | – | Only messages received at/after this ISO 8601 time (UTC if no zone) |
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | yes | – |
| returned | integer | yes | – |
| total | integer | yes | – |
No examples provided.
reconnect 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.
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.
pypi · labmcp-astm-lis
claude mcp add k-dense-ai-labmcp-astm-lis -- uvx labmcp-astm-lis
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 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 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 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 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.
What did VerifyMCP test on the ASTM LIS Analyzer Receiver MCP server?
VerifyMCP ran 15 checks on ASTM LIS Analyzer Receiver, 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 ASTM LIS Analyzer Receiver: 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.