Lab Result Integrity
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Lab Result Integrityscreen this potassium result for delta check and HIL interference"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Lab Result Integrity
Integrity agents for clinical laboratory results. They screen numeric results for problems the laboratory's own data can reveal, assemble a cited, hashed evidence packet for anything suspicious, and queue it for a pathologist. They never release, verify or autoverify a result: release stays with the LIS's validated rules or a human.
Results ─▶ Trend Analysis ─▶ Interference Detection ─▶ Patient-based QC
─▶ Evidence Collection ─▶ Pathologist Review ─▶ Human decisionCapabilities
Capability | Implementation |
Delta checks | Most recent prior result inside a per-analyte window; absolute and/or percent limits, |
Trend analysis | Least-squares slope (units/day) over the analyte's trend window |
Reference and critical ranges | Age bands and sex; unknown sex evaluated against the narrowest combined interval; critical limits make cases |
Interference detection | HIL (hemolysis, icterus, lipemia) index rules per analyte with bias direction and flag/withhold action |
Implausible combinations | Same-specimen rules, e.g. hemolysis with high potassium, K2EDTA carry-over (high K, low Ca), delayed separation, dextrose-line contamination |
Plausibility and units | Physiologically implausible values and unit mismatches hold the result |
Patient-based real-time QC | SMA or EWMA over truncated patient results per instrument and analyte; alarm, look-back list, recovery; shared across replicas |
Evidence packet | Result, prior results, findings with citation text, specimen results, QC snapshot, catalogue digest, provenance record, SHA-256 digest |
Pathologist review queue | Priority and SLA from the catalogue, claims, director override, decisions bound to the evidence digest, escalation of overdue cases |
Agent proposals | Agents may propose a disposition; recorded as |
Governed catalogue | Every threshold cites a source; production refuses an unapproved catalogue |
Never-release invariant | No route, tool or skill releases; the service refuses to start under a policy that would let an agent release or decide |
MCP | Official |
A2A | Agent Card at |
Identity | Enterprise OIDC and agent-identity-fabric credentials; local policy plus fabric authorization, most restrictive wins |
Narrative (optional) | De-identified, advisory draft via the agentic-core model router with ContentGuard on input and output |
Audit | Hash-chained, Ed25519-signed events per replica; verification endpoint |
Observability | Prometheus metrics, OpenTelemetry traces, JSON logs with correlation IDs, SLO alerts, Grafana dashboard |
Shared controls (policy engine, audit chain, model router, content guard, logging, telemetry) come from agentic-core.
Related MCP server: MADMAX Tools Server
Analyte thresholds
All thresholds live in configs/analytes.yaml. The
shipped catalogue is a starter: typical values chosen so the rules run on
synthetic data, each tagged with the source category it should be verified
against (CLSI EP28, GP47, EP33, C56, EP07, Badrick et al. 2019, 42 CFR 493).
They are not clinical guidance. A laboratory replaces them with its own
verified values and marks the catalogue approved; the service refuses a
starter catalogue in production. See
ADR 0003.
Quick start (local)
Requires Docker. No API keys or cloud credentials are needed; all data is synthetic.
docker compose up --build
curl -s localhost:8080/.well-known/agent-card.json | jq .skillsThe compose stack runs PostgreSQL, an OIDC provider standing in for the enterprise IdP, and an OpenTelemetry collector.
Development
uv sync
make check # ruff, black, mypy --strict, bandit, contracts, tests (coverage >= 90%)
make integration # PostgreSQL integration tests (needs LRI_TEST_DATABASE_URL)
make helm terraform audit-depsTest suites: tests/unit (rules, catalogue, PBRTQC, review state machine,
service, auth, fabric client, container), tests/security (attacks mapped to
the threat model), tests/chaos (dependency failures, contention, resume),
tests/performance (latency budgets; locustfile.py for load),
tests/e2e (HTTP lifecycle, MCP, A2A, property-based OpenAPI contract test),
tests/integration (PostgreSQL).
API
Endpoint | Caller | Purpose |
| LIS middleware, agents ( | Screen a batch; returns dispositions, findings, case IDs |
| Staff, agents ( | Result with outcome and review state |
| Staff, agents | Prior results and trend |
| Staff, agents ( | Cases by priority and due time |
| Staff, agents | Case with evidence packet |
| Pathologist, lab director | Human review |
| Agents ( | Proposal pending human approval (202) |
| Staff, agents ( | Moving-statistic state per instrument and analyte |
| Staff, agents | Catalogue governance, digest, sources |
| Auditor, lab director | Verify this replica's audit chain |
| MCP clients | Tools: |
| A2A peers | Skills: |
Full contract: docs/api/openapi.json; JSON Schemas in schemas/.
Deployment
Layer | Location |
Container image |
|
Helm chart |
|
Namespace and secret sync |
|
Cloud infrastructure |
|
See the start-up runbook.
Documentation
Runbooks: startup, monitoring, incident response, PBRTQC alarm, review SLA breach, catalogue change, rollback, disaster recovery
License
Apache-2.0
This server cannot be deployed
Maintenance
Related MCP Connectors
Independent statistical feature evaluation for machine learning and forecasting. ML Referee tests up to 1,000 candidate features in one run against a declared baseline, helping researchers and AI agents decide which inputs to pursue, which bounded feature repairs merit further testing, and where more evidence is needed—without a separate ablation run for every feature. Use the MCP tools to discover input schemas, check access and credits, preflight a dataset, obtain a quote, submit an authorized evaluation, and retrieve structured results and reports. Results are scoped to the submitted evidence and evaluation design; they do not guarantee future model performance. Invite-only beta with manual approval. Public tool discovery requires no authentication; account and evaluation tools require OAuth through approved client connections and available evaluation credits. Connect directly to https://api.mlreferee.com/mcp. Website: https://mlreferee.com Request beta access: https://mlreferee.com/beta Agent setup and documentation: https://mlreferee.com/agents
Remote MCP utilities for agents: structured data, commerce checks, and x402 paid API discovery.
Free read-only tools for agents: agent-readiness audit, TLS/DNS/header checks, MCP search, utils.
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides validated clinical scoring tools for AI agents via MCP, with evidence-based calculators and smart tool discovery.64Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and invoke seven specialist tools—research, finance, risk, compliance, strategy, verification, and report—for orchestrating, validating, and synthesizing enterprise decision workflows.2 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to collect, normalize, and evaluate data from multiple authorized providers through a single local MCP facade, with dynamic provider tool discovery and TypeSafe Jev evidence evaluation.MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP endpoint that lets any AI agent query a histology lab's live case, block and station state via tools such as get_case, list_alerts and cases_delayed, plus a shift_handover prompt and an overview resource. It surfaces workflow alerts, delays and handoff estimates so agents can produce sourced briefs without ever mutating lab data.MIT