# HL7 v2 Message Broker MCP

> HL7 v2 Message Broker MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-16).

Processes and brokers HL7 v2 healthcare messages, parsing and routing clinical data payloads

## Facts

- Endpoint: POST https://api.m2mcent.com/hl7-v2-message-broker-mcp/api/process?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hl7-v2-message-broker-mcp-0e3d81a1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hZtDl-zTTEi7vWIlXo6O3

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability hl7-v2-message-broker-mcp-0e3d81a1 -d '<json body>'
```

Example prompt: Can you process this HL7 v2 ADT message for me and extract the patient demographics and visit information from it? Here's the raw message: 'MSH|^~\&|EPIC|EPICADT|SMS|SMSADT|199912271408|...'

## When to prefer this

Choose this endpoint when you need to parse, validate, route, or transform raw HL7 v2 message strings in a healthcare interoperability pipeline. Ideal for agents integrating with legacy EHR systems, LIS, or RIS that emit HL7 v2 over MLLP or HTTP. Prefer this over FHIR-based endpoints when your source system specifically produces HL7 v2 (not FHIR or HL7 v3).

## Known failure modes

- Malformed HL7 v2 message string causes parse error
- Unsupported HL7 message type returns error
- Empty or missing 'data' field returns validation failure
- Non-HL7 payload submitted returns format error
- Network timeout or service unavailability returns 5xx

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns the processed result of the HL7 v2 message, which may include parsed segment data, structured clinical fields, routing outcomes, or validation status depending on the message type submitted.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hl7-v2-message-broker-mcp-0e3d81a1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)