In-depth architectural comparison of the Dicom Hl7 MCP Server and Heor Agent MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Dicom Hl7 MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Heor Agent MCP
Biology, Medicine and Bioinformatics · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Dicom Hl7 MCP Server if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Heor Agent MCP if your workspace requires Biology, Medicine and Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Dicom Hl7 MCP Server when:
You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: DICOM_HL7_LICENSE_KEY, DICOM_HL7_PACS_AE_TITLE, DICOM_HL7_PACS_HOST, DICOM_HL7_PACS_PORT, DICOM_HL7_LOCAL_AE_TITLE, DICOM_HL7_DICOMWEB_URL, DICOM_HL7_DICOMWEB_TOKEN, DICOM_HL7_DICOMWEB_USERNAME.
The only MCP server bridging DICOM, HL7v2, and FHIR in one package. Cross-standard mapping, Mirth Connect channel generation, vendor private tag decoding (GE, Siemens, Philips), and integration pattern knowledge. Built by a 19-year healthcare IT veteran. pip install dicom-hl7-mcp
HEOR (Health Economics and Outcomes Research) MCP server with 7 tools for literature search across 41 medical data sources (PubMed, NICE, CADTH, ICER, etc.), cost-effectiveness modeling (Markov/PartSA/PSA), and HTA dossier preparation for pharmaceutical and biotech teams.
Tools & Capabilities Breakdown
Dicom Hl7 MCP Server Tools (17)
lookup_dicom_tag
Look up any DICOM tag by number or keyword
explain_dicom_tag
Detailed tag explanation with vendor quirks and gotchas
parse_hl7_message
Parse HL7 v2.x messages into human-readable format
explain_hl7_segment
Explain segment fields, data types, and usage
lookup_hl7_table
Look up HL7 table values (Administrative Sex, Patient Class, etc.)
map_dicom_to_hl7
Map DICOM tags to HL7 v2 fields with conversion notes
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Dicom Hl7 MCP Server is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Heor Agent MCP belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Dicom Hl7 MCP Server when you need capabilities focused on biology, medicine and bioinformatics and Heor Agent MCP when you require tools for biology, medicine and bioinformatics.
Generate realistic sample HL7 messages for testing
+5 more tools listed on main page
Heor Agent MCP Tools (17)
literature_search
Search 44 data sources with a full PRISMA-style audit trail
screen_abstracts
PICO-based relevance scoring and study design classification
risk_of_bias
Cochrane RoB 2 / ROBINS-I / AMSTAR-2 with GRADE RoB domain summary
evidence_network
Build treatment comparison network and assess NMA feasibility
evidence_indirect
Bucher and frequentist NMA with **automatic consistency check** vs direct h2h evidence (NICE DSU TSD 18)
population_adjusted_comparison
MAIC and STC for population-adjusted indirect comparisons
survival_fitting
Fit 5 parametric distributions to KM data (NICE DSU TSD 14)
itc_feasibility
Assess the 3-assumption ITC framework and recommend Bucher / NMA / MAIC / STC / ML-NMR
cost_effectiveness_model
Markov / PartSA / decision-tree CEA with PSA, OWSA, CEAC, EVPI, EVPPI; QALY + evLYG support
budget_impact_model
ISPOR-compliant BIA with year-by-year output and treatment-displacement modelling
hta_dossier
Draft submissions for NICE, EMA, FDA, IQWiG, HAS, and EU JCA — GRADE table uses structured RoB when `rob_results` passed; **inconsistency uses I² when `heterogeneity_per_outcome` passed**; **GRADE upgrading (Guyatt 2011) supported via `upgrading_per_outcome`