Catenix: Lab Analyzer & EHR Connectivity MCP server
com.catenix/lab-connectivitycatenix.comstreamable-httpv1.2.0Scanned
Check if a lab or point-of-care analyzer connects to your EHR or LIS, how, and plan the lab setup.
13 tools: 1 do something that can't be undone, 8 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Catenix: Lab Analyzer & EHR Connectivity MCP server can do
The Catenix: Lab Analyzer & EHR Connectivity MCP server is published by catenix.com, a domain the MCP Registry verified. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_demo) and create or change data (8 tools: check_connectivity, recommend_lab_setup, decode_lab_message, plan_lab_setup and 4 more), but cannot delete data. 4 tools only read.
2 tools bring in text other people can write (search_analyzers and request_demo).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Can't be undone 1Claude Code: ask
request_demoSends the user's demo request to the Catenix team by email; the team replies to the address the user gives.Reads text others writeNo findings
Why it is in this group
- The name "request_demo" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. The Catenix widget may call it only after it has shown the user every field and the user pressed Confirm and send. Do not guess missing fields: ask for them.
Annotations the server declares
- title: Request a demo
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 8Claude Code: ask
check_connectivityUse 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 rety…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote 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.
Annotations the server declares
- title: Check analyzer connectivity
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_qc_westgardUse when someone has quality control (QC) results for a lab or point-of-care test and wants to know whether they break Westgard rules or how they look on a Levey-Jennings chart (e.…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when someone has quality control (QC) results for a lab or point-of-care test and wants to know whether they break Westgard rules or how they look on a Levey-Jennings chart (e.g. 'do these control values fail any Westgard rules?', 'check my QC: mean 5.0, SD 0.1, values ...', 'is this a 2-2s or 4-1s violation?'). Takes control values in run order plus the target mean and SD (or computes them from the values if the user asks) and evaluates 1-2s (warning), 1-3s, 2-2s, R-4s, 4-1s and 10x. Returns z-scores, the rule hits for each point and a plain summary, and draws a Levey-Jennings chart in ChatGPT. Up to 500 values. QC statistics only: not a clinical interpretation of any patient result.
Annotations the server declares
- title: Westgard QC check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
decode_lab_messageUse when someone pastes a message from a lab analyzer, LIS, middleware or EHR interface and wants to know what it says, what a field means, or why the receiving system rejects it (…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when someone pastes a message from a lab analyzer, LIS, middleware or EHR interface and wants to know what it says, what a field means, or why the receiving system rejects it (e.g. 'what does this HL7 ORU mean?', 'why is my EHR rejecting this result message?', 'decode this ASTM output from my analyzer', 'is this POCT1-A2 OBS message valid?'). Accepts HL7 v2 (ORU, ORM, ACK, ADT and others), ASTM E1394 / LIS2-A2 records (H, P, O, R, C, Q, L, with or without E1381 framing and checksums) and POCT1-A2 XML. Returns a field-by-field breakdown (segment or record, field number, name, value, meaning, what an EHR or LIS usually expects) and flags common problems: wrong delimiters or segment terminators, missing MSH-9 or OBX-3 codes, numeric results without units, non-standard abnormal flags, non-LOINC codes, bad checksums. Likely patient identifiers (HL7 PID-3, PID-5, PID-7, PID-11, PID-13 and similar, ASTM patient ID, name and birthdate, POCT1-A2 patient elements) are masked in the output. Tell the user to paste only test or de-identified messages. Nothing is stored or logged. Does not interpret results.
Annotations the server declares
- title: Decode a lab message
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
estimate_time_savedUse when someone wants to know how much staff time manual entry of analyzer results costs them, or would be saved by connecting analyzers to the EHR or LIS (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when someone wants to know how much staff time manual entry of analyzer results costs them, or would be saved by connecting analyzers to the EHR or LIS (e.g. 'we run 80 tests a day and typing each result takes 2 minutes, how much time is that?', 'is it worth interfacing our analyzers?'). Uses only the user's own numbers (tests per day, minutes of manual entry per result, sites, optionally results per test, working days and their own error rate) and returns hours per day, month and year and entries not retyped. Adds no benchmarks, prices or error statistics; without an error rate from the user it makes no error estimate.
Annotations the server declares
- title: Estimate time saved
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
inspection_checklistUse when someone is preparing a lab or point-of-care testing service for an inspection or accreditation and wants to know what inspectors look for (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when someone is preparing a lab or point-of-care testing service for an inspection or accreditation and wants to know what inspectors look for (e.g. 'what do I need for a CLIA inspection?', 'CAP checklist for QC and competency', 'ISO 15189:2022 readiness', 'UK POCT governance checklist'). Returns a practical checklist (quality control, competency, EQA or proficiency testing, document control, audit trail, result reporting, equipment) with the evidence usually asked for, and which Catenix module keeps those records. General guidance, not legal or regulatory advice.
Annotations the server declares
- title: Inspection checklist
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
plan_lab_setupUse when someone lists the analyzers in their lab or clinic and wants a plan for getting all their results into their EHR, LIS or practice system (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when someone lists the analyzers in their lab or clinic and wants a plan for getting all their results into their EHR, LIS or practice system (e.g. 'we have a Sysmex XP-300, an i-STAT and an Afinion 2, how do we connect them to athenahealth?', 'plan the interfaces for our new urgent care lab', 'what do I need on site to connect these analyzers?'). Returns one plan: per analyzer the connection status (Driver built, Connection guide, or Catenix builds the driver, usually within a couple of days), the physical link (serial, network, USB or vendor software), protocol and what is needed on site; the on-site gateway and record-system route; patient matching; and a step-by-step go-live checklist. Renders an interactive Lab Map in ChatGPT. Does not interpret results.
Annotations the server declares
- title: Plan a lab setup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
recommend_lab_setupUse 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 we…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Recommend a setup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
vendor_questionsUse when someone is choosing or buying a LIS, LIMS, POCT middleware or an analyzer-to-EHR interface and wants an RFP or a list of questions to ask vendors (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use when someone is choosing or buying a LIS, LIMS, POCT middleware or an analyzer-to-EHR interface and wants an RFP or a list of questions to ask vendors (e.g. 'what should I ask LIS vendors?', 'RFP questions for lab middleware', 'checklist for buying an HL7 interface'). Returns a copyable, vendor-neutral checklist grouped by connectivity, QC and compliance, security and privacy, data and audit trail, implementation and support, pricing, and contract and exit.
Annotations the server declares
- title: Vendor questions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
compare_optionsUse 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 …No findings
Why it is in this group
- The name "compare_options" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Compare options
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_ehr_integrationUse 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 …No findings
Why it is in this group
- The name "get_ehr_integration" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: EHR integration route
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_platform_capabilityUse 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 comp…No findings
Why it is in this group
- The name "get_platform_capability" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Platform capability
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_analyzersUse when someone wants to know which lab or point-of-care analyzers can be interfaced, or browses by maker or test type (e.g.Reads text others writeNo findings
Why it is in this group
- The name "search_analyzers" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search analyzers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.catenix.com/api/mcp: tools/list returned 13 tools to an anonymous client, including request_demo (irreversible), check_connectivity (write), recommend_lab_setup (write), decode_lab_message (write), plan_lab_setup (write) and 4 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 added, 1 changed.+6 added~1 changedView diff
- Added:check_qc_westgardChanges things
- Added:decode_lab_messageChanges things
- Added:estimate_time_savedChanges things
- Added:inspection_checklistChanges things
- Added:plan_lab_setupChanges things
- Added:vendor_questionsChanges things
- Changed:request_demoCan't be undonedescription
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lab-connectivity https://www.catenix.com/api/mcpclaude mcp add --transport http lab-connectivity https://www.catenix.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lab-connectivity__search_analyzers",
"mcp__lab-connectivity__get_ehr_integration",
"mcp__lab-connectivity__compare_options",
"mcp__lab-connectivity__get_platform_capability"
],
"ask": [
"mcp__lab-connectivity__check_connectivity",
"mcp__lab-connectivity__recommend_lab_setup",
"mcp__lab-connectivity__decode_lab_message",
"mcp__lab-connectivity__plan_lab_setup",
"mcp__lab-connectivity__check_qc_westgard",
"mcp__lab-connectivity__estimate_time_saved",
"mcp__lab-connectivity__inspection_checklist",
"mcp__lab-connectivity__vendor_questions",
"mcp__lab-connectivity__request_demo"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lab-connectivity. Review it before you use it.
Capability tags behind 2 rules
- mcp__lab-connectivity__search_analyzers untrusted-input
- mcp__lab-connectivity__request_demo untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.catenix/lab-connectivity/verify?hash=71a55da125100b8469064cb53a1aac5960204f58248aa1dca37b80fbe2e1a54a" | jq -e '.changed == false'Pinned hash 71a55da12510, from Nov 18, 2026, 12:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.catenix/lab-connectivity/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.catenix/lab-connectivity)Source: MCP Registry. Synced Nov 18, 2026, 12:17 UTC.
Catenix: Lab Analyzer & EHR Connectivity MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Catenix: Lab Analyzer & EHR Connectivity MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Catenix: Lab Analyzer & EHR Connectivity MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Catenix: Lab Analyzer & EHR Connectivity MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_demo.
What tools does the Catenix: Lab Analyzer & EHR Connectivity MCP server have?
- 13 tools: 1 irreversible, 8 write, 4 read. request_demo, check_connectivity, recommend_lab_setup, decode_lab_message, plan_lab_setup, check_qc_westgard, estimate_time_saved, inspection_checklist and 5 more.
Does the Catenix: Lab Analyzer & EHR Connectivity MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Catenix: Lab Analyzer & EHR Connectivity MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Catenix: Lab Analyzer & EHR Connectivity MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.