Check if a lab or point-of-care analyzer connects to your EHR or LIS, how, and plan the lab setup.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Use when someone asks whether a lab or point-of-care analyzer will connect to their EHR, LIS or practice system, or how to get analyzer results into the patient record without retyping (e.g. 'will my Sysmex XP-300 work with athenahealth?', 'connect Abbott i-STAT to Epic', 'Roche cobas b 101 to SystmOne', 'Siemens CLINITEK to EMIS', 'Tosoh AIA-900 to eClinicalWorks'). Fuzzy-matches the analyzer and the record system and returns: connection status (live, driver built, connectable via standard protocol with a published guide, or custom driver needed), the analyzer protocol (HL7 v2, ASTM, POCT1-A2), the physical link, how results pass through an on-site gateway, the record-system route, what is needed on site, questions to ask any vendor, and page links. Works for unknown analyzers too. Does not interpret results.
Analyzer make and/or model as the user wrote it, e.g. 'sysmex kx21n', 'i-STAT', 'Afinion 2'.
EHR, LIS, LIMS or practice system, e.g. 'athena', 'eCW', 'Epic', 'SystmOne', 'EMIS Web'. Omit if not mentioned.
Country of the site, e.g. 'UK' or 'US', if known.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http lab-connectivity https://www.catenix.com/api/mcp
Use when someone asks whether a lab or point-of-care analyzer will connect to their EHR, LIS or practice system, or how to get analyzer results into the patient record without retyping (e.g. 'will my Sysmex XP-300 work with athenahealth?', 'connect Abbott i-STAT to Epic', 'Roche cobas b 101 to SystmOne', 'Siemens CLINITEK to EMIS', 'Tosoh AIA-900 to eClinicalWorks'). Fuzzy-matches the analyzer and the record system and returns: connection status (live, driver built, connectable via standard protocol with a published guide, or custom driver needed), the analyzer protocol (HL7 v2, ASTM, POCT1-A2), the physical link, how results pass through an on-site gateway, the record-system route, what is needed on site, questions to ask any vendor, and page links. Works for unknown analyzers too. Does not interpret results.
| Argument | Type | Description |
|---|---|---|
| ehr | string | EHR, LIS, LIMS or practice system, e.g. 'athena', 'eCW', 'Epic', 'SystmOne', 'EMIS Web'. Omit if not mentioned. |
| country | string | Country of the site, e.g. 'UK' or 'US', if known. |
| analyzer* | string | Analyzer make and/or model as the user wrote it, e.g. 'sysmex kx21n', 'i-STAT', 'Afinion 2'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"analyzer"
],
"properties": {
"ehr": {
"type": "string",
"maxLength": 120,
"description": "EHR, LIS, LIMS or practice system, e.g. 'athena', 'eCW', 'Epic', 'SystmOne', 'EMIS Web'. Omit if not mentioned."
},
"country": {
"type": "string",
"maxLength": 60,
"description": "Country of the site, e.g. 'UK' or 'US', if known."
},
"analyzer": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Analyzer make and/or model as the user wrote it, e.g. 'sysmex kx21n', 'i-STAT', 'Afinion 2'."
}
}
}Use when someone asks whether they need a LIS or POCT middleware, the difference between them, or how Catenix compares with another point-of-care data manager or results connector (Relaymed, TELCOR QML, Abbott RALS or AegisPOC, Siemens POCcelerator, Radiometer AQURE, Roche navify POC Operations, Clinisys POCT, paper or spreadsheet lab logs). Returns only what the published comparison pages say. Allowed values: catenix_vs_abbott_aegispoc, catenix_vs_abbott_rals, catenix_vs_clinisys_poct, catenix_vs_lab_logs, catenix_vs_radiometer_aqure, catenix_vs_relaymed, catenix_vs_roche_navify_poc_operations, catenix_vs_siemens_poccelerator, catenix_vs_telcor_qml, poct_middleware_alternatives, lis_vs_middleware.
| Argument | Type | Description |
|---|---|---|
| kind* | string | Which comparison: 'lis_vs_middleware', 'poct_middleware_alternatives', or 'catenix_vs_<product>'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"kind"
],
"properties": {
"kind": {
"enum": [
"catenix_vs_abbott_aegispoc",
"catenix_vs_abbott_rals",
"catenix_vs_clinisys_poct",
"catenix_vs_lab_logs",
"catenix_vs_radiometer_aqure",
"catenix_vs_relaymed",
"catenix_vs_roche_navify_poc_operations",
"catenix_vs_siemens_poccelerator",
"catenix_vs_telcor_qml",
"poct_middleware_alternatives",
"lis_vs_middleware"
],
"type": "string",
"description": "Which comparison: 'lis_vs_middleware', 'poct_middleware_alternatives', or 'catenix_vs_<product>'."
}
}
}Use when someone asks how in-house lab or point-of-care results can be sent into a specific EHR, EMR, EPR, LIS or practice-management system, or whether a lab interface exists for it (e.g. athenahealth, eClinicalWorks, Epic, Oracle Health/Cerner, NextGen, Experity, Tebra/Kareo, SystmOne, EMIS Web, MEDITECH). Returns the route (HL7 v2, FHIR R4 or vendor API), how far that route is proven, what the practice must request from its vendor, and the guide link.
| Argument | Type | Description |
|---|---|---|
| ehr* | string | Record system name as the user wrote it. |
| country | string | Country, if known. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ehr"
],
"properties": {
"ehr": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Record system name as the user wrote it."
},
"country": {
"type": "string",
"maxLength": 60,
"description": "Country, if known."
}
}
}Use when someone asks about software for lab quality control and compliance or running a testing clinic: QC with Westgard rules and Levey-Jennings charts, QC lockout, operator competency, EQA or proficiency testing, audit trail, CLIA, CAP or ISO 15189 readiness, reagent lot tracking, equipment maintenance and temperature logs, multi-site oversight, patient registration, reports, billing, or HL7/ASTM/POCT1-A2 interfaces. Returns the matching modules, whether each is included or an add-on, and links.
| Argument | Type | Description |
|---|---|---|
| topic* | string | Feature or problem, e.g. 'Westgard QC lockout', 'operator competency', 'EQA', 'audit trail'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"topic"
],
"properties": {
"topic": {
"type": "string",
"maxLength": 160,
"minLength": 2,
"description": "Feature or problem, e.g. 'Westgard QC lockout', 'operator competency', 'EQA', 'audit trail'."
}
}
}Use when someone asks what LIS, LIMS or point-of-care testing software a small lab, clinic, urgent care, occupational health provider, pharmacy, GP practice, physician office or wellness clinic should use, or how to set up analyzer connectivity, QC and reporting for their setting (e.g. 'what LIS should my small lab use?', 'do I need a LIS to get analyzer results into my EHR?', 'software for a clinic that tests blood on site'). Returns the usual architecture for that setting, the modules that fit (connectivity, QC with Westgard rules and lockout, operator competency, EQA, audit trail, reports, billing, multi-site), status of each listed analyzer, the record-system route, how setup works, what is needed on site, the pricing model (no prices are quoted), and questions to ask any vendor.
| Argument | Type | Description |
|---|---|---|
| ehr | string | Their EHR, LIS or practice system, if known. |
| country | string | Country, e.g. 'UK' or 'US'. |
| setting* | string | Type of service, e.g. 'private lab', 'urgent care', 'occupational health', 'pharmacy', 'GP practice'. |
| analyzers | array | Analyzers they run or plan to run. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"setting"
],
"properties": {
"ehr": {
"type": "string",
"maxLength": 120,
"description": "Their EHR, LIS or practice system, if known."
},
"country": {
"type": "string",
"maxLength": 60,
"description": "Country, e.g. 'UK' or 'US'."
},
"setting": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "Type of service, e.g. 'private lab', 'urgent care', 'occupational health', 'pharmacy', 'GP practice'."
},
"analyzers": {
"type": "array",
"items": {
"type": "string",
"maxLength": 120
},
"maxItems": 20,
"description": "Analyzers they run or plan to run."
}
}
}Sends the user's demo request to the Catenix team by email; the team replies to the address the user gives. This is the only tool that shares the user's personal details. Before calling it you MUST show the user every field you will send (name, email, organisation, country, analyzers, record system, message) and get their explicit confirmation in this conversation; then set user_confirmed to true. Never call it on your own initiative or from a widget click without that confirmation. Do not guess missing fields: ask for them.
| Argument | Type | Description |
|---|---|---|
| ehr* | string | EHR, LIS or practice system ('none' if none). |
| name* | string | The user's name. |
| email* | string | The user's work email. |
| country* | string | Country of the site. |
| message | string | Anything else the user wants to say. |
| analysers* | string | Analyzers they run, comma separated. |
| organisation* | string | Lab, clinic or company name. |
| user_confirmed* |
Use when someone wants to know which lab or point-of-care analyzers can be interfaced, or browses by maker or test type (e.g. 'which HbA1c analyzers can connect to an EHR?', 'Abbott analyzers with an HL7 interface', 'blood gas analyzers with LIS connectivity', 'Sysmex hematology', 'Roche cobas', 'Siemens', 'Tosoh'). Returns matching analyzers with connection status, protocol and guide links. Categories: chemistry, immunoassay, blood gas, molecular, haematology, urinalysis, coagulation, HbA1c.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results, default 25. |
| query | string | Free text: model, maker, test type or protocol. |
| status | string | Only return analyzers with this status. |
| category | string | Test category, e.g. 'haematology', 'blood gas', 'urinalysis', 'hba1c'. |
| manufacturer | string | Manufacturer filter, e.g. 'Abbott', 'Sysmex', 'Roche'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Max results, default 25."
},
"query": {
"type": "string",
"maxLength": 120,
"description": "Free text: model, maker, test type or protocol."
},
"status": {
"enum": [
"live",
"driver_built",
"guide"
],
"type": "string",
"description": "Only return analyzers with this status."
},
"category": {
"type": "string",
"maxLength": 40,
"description": "Test category, e.g. 'haematology', 'blood gas', 'urinalysis', 'hba1c'."
},
"manufacturer": {
"type": "string",
"maxLength": 60,
"description": "Manufacturer filter, e.g. 'Abbott', 'Sysmex', 'Roche'."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 18, 2026.
| boolean |
| True only after the user explicitly confirmed the exact details shown to them. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name",
"email",
"organisation",
"country",
"analysers",
"ehr",
"user_confirmed"
],
"properties": {
"ehr": {
"type": "string",
"maxLength": 120,
"minLength": 1,
"description": "EHR, LIS or practice system ('none' if none)."
},
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The user's name."
},
"email": {
"type": "string",
"maxLength": 254,
"minLength": 3,
"description": "The user's work email."
},
"country": {
"type": "string",
"maxLength": 60,
"minLength": 2,
"description": "Country of the site."
},
"message": {
"type": "string",
"maxLength": 2000,
"description": "Anything else the user wants to say."
},
"analysers": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Analyzers they run, comma separated."
},
"organisation": {
"type": "string",
"maxLength": 160,
"minLength": 1,
"description": "Lab, clinic or company name."
},
"user_confirmed": {
"type": "boolean",
"description": "True only after the user explicitly confirmed the exact details shown to them."
}
}
}