ImOnFHIR

com.imonfhir/siteVersion 1.0.0

imonfhir.com tools: HL7 digest, Jira status, PAS validation, IG and payload compare, rule evidence.

Status

Responds242 msNov 14, 2026, 14:01 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:01 UTC
Latency: 242 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://imonfhir.com/api/v1/mcpResponds242 msNov 14, 2026, 14:01 UTC

No sign-in

Claude Code

claude mcp add --transport http site https://imonfhir.com/api/v1/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: site
Remote MCP server URL: https://imonfhir.com/api/v1/mcp

Cursor

{
  "mcpServers": {
    "site": {
      "url": "https://imonfhir.com/api/v1/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"site","type":"http","url":"https://imonfhir.com/api/v1/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

7 tools

Tools of ImOnFHIR
	Description		Read-only	Idempotent	Open world
`compare_igs`Compare two implementation guides, each "packageId#version": one guide at two versions (version diff) or two guides (stack compare). Over MCP the answer is a bounded summary (the risk level and, in plain words, the rule that set it; counts per change type, a change-type by impact breakdown, the profiles carrying the most breaking changes, what moved in value set definitions, the most serious findings, and where the whole report is); POST /api/v1/compare returns the whole report.	Compare two implementation guides, each "packageId#version": one guide at two versions (version diff) or two guides (stack compare). Over MCP the answer is a bounded summary (the risk level and, in plain words, the rule that set it; counts per change type, a change-type by impact breakdown, the profiles carrying the most breaking changes, what moved in value set definitions, the most serious findings, and where the whole report is); POST /api/v1/compare returns the whole report.	No	Yes	Yes	No
`compare_payloads`Compare two synthetic FHIR payloads (a resource or a Bundle each, 1 MB at most per side) and report where they differ: which rows are missing or extra, which field paths changed, and counts. It returns no field values; it lists up to 200 rows and 300 field paths (the paths come from the key names in the payloads) and counts the rest. Synthetic data only. The payloads are sent to imonfhir.com for the call and the site does not store them; the browser Compare tool at /lab/compare keeps them on your machine.	Compare two synthetic FHIR payloads (a resource or a Bundle each, 1 MB at most per side) and report where they differ: which rows are missing or extra, which field paths changed, and counts. It returns no field values; it lists up to 200 rows and 300 field paths (the paths come from the key names in the payloads) and counts the rest. Synthetic data only. The payloads are sent to imonfhir.com for the call and the site does not store them; the browser Compare tool at /lab/compare keeps them on your machine.	No	Yes	Yes	No
`explain_finding`The evidence behind a semantic validator rule, not an explanation of it. Give rule_id (a rule id such as PAS-SEM-PROV-001) and get the rule's id, version, title, description, source, category and default severity as the validator states them, plus, only when the rule's explanation entry declares anchors that all resolve, the HL7 statements for them: package, version, key, conformance word, HL7's statement text verbatim (its markdown) and the sha256 of that text. It abstains, with the reason, when no anchor is committed or one does not resolve. 0 of 17 rule explanations have committed anchors; a rule id abstains until its anchors are committed. Or give requirement ({packageId, version, key}) and get that one HL7 statement the same way. An unknown package, version or key is an error, and so is a package version that has a catalog but no committed statement text. Statement text is committed for hl7.fhir.us.davinci-pas@2.2.1; a package version that has a catalog but no committed text is an error. It also returns an instruction block telling your assistant how to use the evidence. It calls nothing outside this site. Prose your assistant writes around the passages is not controlled by ImOnFHIR.	The evidence behind a semantic validator rule, not an explanation of it. Give rule_id (a rule id such as PAS-SEM-PROV-001) and get the rule's id, version, title, description, source, category and default severity as the validator states them, plus, only when the rule's explanation entry declares anchors that all resolve, the HL7 statements for them: package, version, key, conformance word, HL7's statement text verbatim (its markdown) and the sha256 of that text. It abstains, with the reason, when no anchor is committed or one does not resolve. 0 of 17 rule explanations have committed anchors; a rule id abstains until its anchors are committed. Or give requirement ({packageId, version, key}) and get that one HL7 statement the same way. An unknown package, version or key is an error, and so is a package version that has a catalog but no committed statement text. Statement text is committed for hl7.fhir.us.davinci-pas@2.2.1; a package version that has a catalog but no committed text is an error. It also returns an instruction block telling your assistant how to use the evidence. It calls nothing outside this site. Prose your assistant writes around the passages is not controlled by ImOnFHIR.	No	Yes	Yes	No
`get_digest_item`One digest item in full: each claim (question, outcome, impact, stage, next step) with its own evidence record, plus HL7 Jira statuses and canonical_url.	One digest item in full: each claim (question, outcome, impact, stage, next step) with its own evidence record, plus HL7 Jira statuses and canonical_url.	No	Yes	Yes	No
`get_jira_status`Up to 50 HL7 Jira keys: status, resolved, resolution, last_verified with its jira_verified evidence record, lifecycle stage, source_url (HL7 Jira) and the canonical_url of public items that cite it. "applied" is not "published".	Up to 50 HL7 Jira keys: status, resolved, resolution, last_verified with its jira_verified evidence record, lifecycle stage, source_url (HL7 Jira) and the canonical_url of public items that cite it. "applied" is not "published".	No	Yes	Yes	No
`search_digest`Search the public digest of HL7 standards discussions. Returns at most 20 items, each with every claim's evidence record and canonical_url — no summary text. Use get_digest_item for one item in full.	Search the public digest of HL7 standards discussions. Returns at most 20 items, each with every claim's evidence record and canonical_url — no summary text. Use get_digest_item for one item in full.	No	Yes	Yes	No
`validate_bundle`Validate a synthetic Da Vinci PAS Submit Bundle with the ImOnFHIR validator. Synthetic payloads only. Never send real patient data. Findings describe a synthetic Bundle. Body cap 2 MB, 10 calls per minute.	Validate a synthetic Da Vinci PAS Submit Bundle with the ImOnFHIR validator. Synthetic payloads only. Never send real patient data. Findings describe a synthetic Bundle. Body cap 2 MB, 10 calls per minute.	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 13, 2026
Updated: Nov 13, 2026
Website: https://imonfhir.com/agents⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Project managementSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing