Skip to content

ImOnFHIR MCP server

com.imonfhir/imonfhirimonfhir.comstreamable-httpv1.0.0Scanned

Validate synthetic PAS Bundles, compare IGs and payloads, quote PAS requirements, search HL7 digest

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the ImOnFHIR MCP server can do

The ImOnFHIR MCP server is published by imonfhir.com, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

3 tools bring in text other people can write (search_digest, get_digest_item and get_jira_status).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • compare_igsCompare two implementation guides, each "packageId#version": one guide at two versions (version diff) or two guides (stack compare).No findings

    Why it is in this group

    • The name "compare_igs" says "compare": a word for reading.
    Description, as the server wrote it
    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 (counts per change type, the most serious findings, and where the whole report is); POST /api/v1/compare returns the whole report.

    Annotations the server declares

    • title: Compare two IGs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • compare_payloadsCompare 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, a…No findings

    Why it is in this group

    • The name "compare_payloads" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Compare two payloads
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • explain_findingThe evidence behind a semantic validator rule, not an explanation of it.No findings

    Why it is in this group

    • The name "explain_finding" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Evidence for a rule or a requirement
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_digest_itemOne digest item in full: each claim (question, outcome, impact, stage, next step) with its own evidence record, plus HL7 Jira statuses and canonical_url.Reads text others writeNo findings

    Why it is in this group

    • The name "get_digest_item" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read one digest item
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_jira_statusUp 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 i…Reads text others writeNo findings

    Why it is in this group

    • The name "get_jira_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • title: HL7 Jira status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_digestSearch the public digest of HL7 standards discussions.Reads text others writeNo findings

    Why it is in this group

    • The name "search_digest" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "discussion": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the standards digest
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_bundleValidate a synthetic Da Vinci PAS Submit Bundle with the ImOnFHIR validator.No findings

    Why it is in this group

    • The name "validate_bundle" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate a PAS bundle
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__imonfhir__search_digest",
      "mcp__imonfhir__get_digest_item",
      "mcp__imonfhir__get_jira_status",
      "mcp__imonfhir__validate_bundle",
      "mcp__imonfhir__compare_igs",
      "mcp__imonfhir__compare_payloads",
      "mcp__imonfhir__explain_finding"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as imonfhir. Review it before you use it.

Capability tags behind 3 rules
  • mcp__imonfhir__search_digest untrusted-input
  • mcp__imonfhir__get_digest_item untrusted-input
  • mcp__imonfhir__get_jira_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.imonfhir/imonfhir/verify?hash=0e6b60f889ad9d0a11085992a2b2411bbd37b802ef7ab6eca392eaeb449c3042" | jq -e '.changed == false'

Pinned hash 0e6b60f889ad, from Nov 13, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.imonfhir/imonfhir/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.imonfhir/imonfhir
[![Anlyon Radar](https://radar.anlyon.com/badge/com.imonfhir/imonfhir.svg)](https://radar.anlyon.com/servers/com.imonfhir/imonfhir)

Source: MCP Registry. Synced Nov 13, 2026, 22:17 UTC.

ImOnFHIR MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ImOnFHIR MCP server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the ImOnFHIR MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ImOnFHIR MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ImOnFHIR MCP server have?

7 tools: 7 read. search_digest, get_digest_item, get_jira_status, validate_bundle, compare_igs, compare_payloads and explain_finding.

Does the ImOnFHIR MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ImOnFHIR MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ImOnFHIR MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.