ImOnFHIR
REMOTE · IMONFHIR.COM
imonfhir.com tools: HL7 digest, Jira status, PAS validation, IG and payload compare, rule evidence.
Available components
Last scanned (13 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1686 tokens (~210/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- Tool “validate_bundle” rewrote its description, which is the text the model reads security
- 15 Nov 26 +1
- Tool “validate_bundle” rewrote its description, which is the text the model reads security
- Schema quality: 185 → 206 ▼ functional
- New tool “get_validation_findings” functional
- 14 Nov 26 0
- Tool “compare_igs” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://imonfhir.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=imonfhir.com | CN=YR1,O=Let's Encrypt,C=US | 12 Nov 2026 | 10 Feb 2027 | RSA 2048 | SHA256-RSA | 60d0b6d564e0e57155c5e4194537c8d3ccc |
| SANs: imonfhir.com, www.imonfhir.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of imonfhir.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| imonfhir.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://va.vercel-scripts.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://va.vercel-scripts.com https://vitals.vercel-insights.com https://www.google-analytics.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://imonfhir.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://imonfhir.com/api/v1/mcp | HTTPS enforced | 308 | https://imonfhir.com/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_igs Compare two IGs ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ig_a | string | yes | e.g. "hl7.fhir.us.davinci-pas#2.0.1" |
| ig_b | string | yes | e.g. "hl7.fhir.us.davinci-pas#2.1.0" |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | – | – |
| comparison_notes | array | – | – |
| comparison_status | string|null | – | – |
| counts | object | yes | – |
| findings_listed | integer | yes | – |
| findings_omitted | integer | yes | – |
| full_report | object | yes | – |
| ig_a | string | yes | – |
| ig_b | string | yes | – |
| mode | – | yes | – |
| notice | string | yes | – |
| risk | object|null | – | – |
| summary | – | yes | – |
| top_findings | array | yes | – |
| top_profiles | object | – | – |
| truncated | boolean | yes | – |
| valueset_definition_changes | array | – | – |
| valueset_unchanged_unlisted | integer | – | – |
No examples provided.
compare_payloads Compare two payloads ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | object|string | yes | A FHIR resource or Bundle (a JSON object, or a string holding one). Synthetic only. |
| b | object|string | yes | The payload to compare it with, in the same form. |
| Name | Type | Req | Description |
|---|---|---|---|
| identical | boolean | yes | – |
| notice | string | yes | – |
| paths_listed | integer | yes | – |
| paths_omitted | integer | yes | – |
| rows | array | yes | – |
| rows_listed | integer | yes | – |
| rows_omitted | integer | yes | – |
| stats | object | yes | – |
| truncated | boolean | yes | – |
No examples provided.
explain_finding Evidence for a rule or a requirement ~367
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.
| Name | Type | Req | Description |
|---|---|---|---|
| requirement | object | – | One HL7 statement: its package id, version and statement key, e.g. hl7.fhir.us.davinci-pas, 2.2.1, ainfo-3. Give this or rule_id, not both. |
| rule_id | string | – | A semantic rule id, e.g. PAS-SEM-PROV-001. Give this or requirement, not both. |
| Name | Type | Req | Description |
|---|---|---|---|
| abstain | object | – | – |
| instruction_block | object | yes | – |
| mode | – | yes | – |
| notice | string | yes | – |
| outcome | – | yes | – |
| passages | array | yes | – |
| rule | object | – | – |
No examples provided.
get_digest_item Read one digest item ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The item id from search_digest. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | – |
| canonical_url | string | yes | – |
| claims | array | yes | – |
| id | string | yes | – |
| jira | array | yes | – |
| last_activity | string|null | yes | – |
| source_url | string|null | yes | – |
| stage | string|null | yes | – |
| stage_evidence | object|null | yes | – |
| standards | array | yes | – |
| title | string|null | yes | – |
| workgroup | string|null | yes | – |
No examples provided.
get_jira_status HL7 Jira status ~71
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".
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | – |
| statuses | array | yes | – |
No examples provided.
get_validation_findings Every finding of a large validation ~206
Every issue of one large validate_bundle result, a page at a time. Give it the result_id from a validate_bundle summary; it reads what validate_bundle kept (the findings, never the bundle) for 1 hour, so the bundle is not sent again and the validator does not run again. The issues come in the order POST /api/v1/validate returns them; call again with page.next_offset until it is null. Optional severity filters to fatal, error, warning or information. An unknown or expired result_id is an error: run validate_bundle again. Synthetic payloads only. Never send real patient data. Findings describe a synthetic Bundle. 60 calls per minute; MCP only.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | Where the page starts, counting the issues chosen (default 0); use page.next_offset. |
| result_id | string | yes | From a validate_bundle summary (result_id or next_steps). |
| severity | string | – | Only issues of this severity. |
| Name | Type | Req | Description |
|---|---|---|---|
| clipped | array | yes | – |
| expires_at | string | yes | – |
| findings_digest | string | yes | – |
| issues | array | yes | – |
| next_steps | array | yes | – |
| notice | string | yes | – |
| page | object | yes | – |
| pas_version | string|null | yes | – |
| result_id | string | yes | – |
| severity | string|null | yes | – |
No examples provided.
search_digest Search the standards digest ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | Words to match in the title, work group or HL7 Jira keys. |
| since | string | – | ISO date; only items with activity on or after it. |
| workgroup | string | – | A work group (the feed's list slug, e.g. "da-vinci-pas"). An unknown one is an error. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | – |
| count | integer | yes | – |
| items | array | yes | – |
No examples provided.
validate_bundle Validate a PAS bundle ~278
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. Over MCP every answer carries `verdict`: the validator's own readiness verdict, the one its Lab shows (readiness, a one-sentence statement, its readiness dimensions and its consolidated counts); read it first. Then `summary`: false means the whole OperationOutcome is in `outcome`; true means it was over 100,000 characters, so the answer is a bounded summary instead (the coverage note; distinct problems by severity, a problem the validator's layers report twice counted once, with the raw counts beside them; counts by issue code, rule family and resource; the PAS profile versions the issues cite; the 25 most serious kinds of finding, and how many were not listed). A summary's findings (never the bundle) are kept 1 hour: get_validation_findings pages every issue with the result_id it gives. POST /api/v1/validate returns the whole OperationOutcome.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | A FHIR Bundle (resourceType "Bundle"). Synthetic only. |
| ig | string | – | – |
| version | string | – | A PAS version the validator allows; omitted, the default. |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | – | – |
| coverage | object | – | – |
| expires_at | string|null | – | – |
| findings_digest | string|null | – | – |
| findings_listed | integer | – | – |
| findings_omitted | integer | – | – |
| full_report | object | – | – |
| ig | – | yes | – |
| instruction_block | object | – | – |
| key_findings | array | – | – |
| next_steps | array | – | – |
| notice | string | yes | – |
| outcome | object | – | Present only when summary is false. |
| pas_profile_versions_cited | array | – | – |
| requestId | string | yes | – |
| result_id | string|null | – | The id get_validation_findings reads; null when the result could not be kept (see store_note). |
| store_note | string|null | – | – |
| summary | boolean | yes | false: the whole OperationOutcome is in outcome. true: it was too long to send whole; this is a bounded summary. |
| summary_notice | string | – | – |
| truncated | boolean | – | – |
| verdict | object | yes | The validator product's own readiness verdict, the one its Lab shows; read verdict.statement first. |
| version | string|null | yes | – |
| version_note | string|null | – | – |
No examples provided.
How do I install the ImOnFHIR MCP server?
ImOnFHIR is a hosted endpoint at https://imonfhir.com/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · imonfhir.com
claude mcp add --transport http com-imonfhir-site 'https://imonfhir.com/api/v1/mcp'
What is the ImOnFHIR MCP server?
ImOnFHIR is an MCP server listed in the public MCP registry as com.imonfhir/site. imonfhir.com tools: HL7 digest, Jira status, PAS validation, IG and payload compare, rule evidence. This page covers its hosted endpoint (https://imonfhir.com/api/v1/mcp).
Is the ImOnFHIR MCP server safe to use?
ImOnFHIR scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ImOnFHIR MCP server expose?
ImOnFHIR exposes 8 tools: search_digest, get_digest_item, get_jira_status, validate_bundle, get_validation_findings, and 3 more. Their descriptions and schemas cost roughly 1,444 tokens of context every time the server is loaded.
Does the ImOnFHIR MCP server require authentication?
No. We connected to ImOnFHIR without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ImOnFHIR MCP server still maintained?
ImOnFHIR is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ImOnFHIR MCP server?
VerifyMCP ran 13 checks on ImOnFHIR, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.