Hosted MCP server

Connect AI agents to Haem.io diagnostic decision support

The Haem.io MCP server gives approved AI clients a narrow, audited tool interface for parsing haematology reports, routing myeloid cases, checking guardrails, and returning explainable risk support.

Request access View classifier logic

Remote MCP endpoint

https://mcp.haem.io/mcp

Transport: Hosted HTTP MCP
Auth: haem.io OAuth entitlement
Default mode: Deterministic tools, AI review off

Clinical decision support only. Final diagnosis requires qualified clinician review.

How users connect

Designed for MCP-capable clinical AI workflows

1. Request access

Create or use an active haem.io account, then request MCP access. We approve MCP separately from normal app login because agentic diagnostic access needs tighter control.

2. Sign in with approved OAuth

Use https://mcp.haem.io/mcp as the server URL in your MCP-capable client. OAuth tokens must include the MCP audience, diagnostic scopes, and a haem.io MCP entitlement.

3. Keep the agent in decision-support mode

Agents should call capabilities first, parse reports before classification, and stop at clinician-confirmation states instead of inventing missing clinical facts.

Access model

Login is necessary, approval is separate

A haem.io account proves who the user is. MCP entitlement controls whether that user can connect clinical AI agents to the diagnostic tools.

haem.io account

Required for user-facing OAuth access. The account must be active.

MCP entitlement

Required separately from normal app access. Approved users have MCP access enabled on their haem.io profile.

Diagnostic scopes

The OAuth token must include the requested tool scopes, such as diagnostic:parse or diagnostic:classify.

Service tokens

Reserved for approved beta, service, or integration testing workflows and should use the narrowest practical scope.

Tool surface

Narrow tools, explicit scopes

Agents do not receive source code, filesystem access, database mutation, or arbitrary function execution. Each call returns an audit run ID where a parse or classification workflow is performed.

parse_haematology_report

Extract structured marrow, flow, genetics, and warning fields from free-text reports.

diagnostic:parse

classify_myeloid_case

Run the audited myeloid orchestrator for AML, MDS, CML, and CMML decision support.

diagnostic:classify

calculate_risk

Calculate supported ELN and IPSS risk outputs from structured case data.

diagnostic:risk

evaluate_guardrails

Return deterministic safety checks, missing-data gates, and Imandra diagnostics.

diagnostic:guardrails

get_diagnostic_capabilities

Show supported disease areas, schemes, required fields, and non-covered areas.

diagnostic:*

Clinical scope

Clear boundaries for safer agent use

Supported in v1AML, MDS, CML, and CMML myeloid decision support under WHO 2022 and ICC 2022.

Risk supportELN 2022 intensive AML, ELN 2024 non-intensive AML, IPSS-M, and IPSS-R where data are available.

GuardrailsFlow cytometry gates, confirmation sentinels, missing-data warnings, parser diagnostics, and Imandra parity checks.

Not v1 coverageMPN is documented as future work. Lymphoid diagnosis, MPAL final diagnosis, and autonomous final reporting are out of scope.

Client setup

Connection details for early adopters

Add the remote MCP server

Use https://mcp.haem.io/mcp as the server URL in your MCP-capable client. The transport is hosted HTTP MCP with JSON-RPC tool calls.

Authorize with haem.io

Complete the haem.io/Auth0 OAuth flow. Access succeeds only for active haem.io users with MCP enabled.

Start with capabilities

Ask the agent to call get_diagnostic_capabilities before parsing or classification so it understands scope and stopping rules.

ChatGPT and custom GPT actions

Use the remote server URL when MCP connectors are available for your workspace. OAuth sign-in is the production access pattern for approved haem.io users.

Server URL: https://mcp.haem.io/mcp
Auth: haem.io OAuth with MCP access enabled

Claude and MCP-compatible clients

Add Haem.io as a remote HTTP MCP server and pass the access token in the Authorization header if your client supports bearer-token MCP servers.

Authorization: Bearer <haemio_mcp_token>
Content-Type: application/json

Generic HTTP test

For technical validation, call the JSON-RPC initialize method, then list tools with an approved access token.

POST https://mcp.haem.io/mcp
{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }