Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Minos Health is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Polish ICD-10, ICD-9 PL, ICD-11 PL codes and NFZ JGP hospital grouping from official sources.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http minos-health-mcp https://minoshealth.pl/mcp
# 2 — ask your agent for something these tools do
# get_service_info, search_codes, get_code and 9 more
Minos Health costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MIAll 1 server
minoshealth1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http minos-health-mcp https://minoshealth.pl/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the releases Minos serves: ICD-10 PL, ICD-9 PL and ICD-11 PL versions, validity and licences, JGP grouping availability and knowledge horizon, and the disclaimer. Call it first to learn which service dates are covered; use get_source_status to see what publishers released since.
No parameter schema on file.
Search ICD-10 PL diagnoses, ICD-9 PL procedures, JGP groups and, when asked, pre-released ICD-11 PL by code or Polish words (diacritics optional). Each hit has its code, title, path and JGP group count; JGP groups are always searched in today's catalog. Open a hit with get_code or get_jgp_group; walk a hierarchy with browse_codes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A code or Polish words, e.g. J18.9 or zapalenie płuc. |
| systems | array | no | Dictionaries to search; add icd11-pl only when asked. |
| service_date | no | Day of care, YYYY-MM-DD; picks the release in force. Default today in Poland. | |
| limit | integer | no | Hits per dictionary. |
Get one ICD-10 PL, ICD-9 PL or ICD-11 PL code as its page shows it: title, hierarchy, children, notes, attributes, ICD-9 rank, WHO map rows and, for ICD-10 and ICD-9, the JGP groups whose attachment 9 lists name it on service_date. Find the code with search_codes first; open a listed group with get_jgp_group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| system | yes | Classification of the code. | |
| code | yes | The code as printed, e.g. J18.9, 53.03 or BA00. | |
| service_date | no | Day of care, YYYY-MM-DD; picks the release in force. Default today in Poland. |
List one level of ICD-10 PL, ICD-9 PL or ICD-11 PL: the chapters when parent and node are omitted, else the children of parent or of a node id from an earlier listing (ICD-11 blocks have a node id, no code). Levels stop at 400 entries with truncated=true. Use search_codes for words, get_code for one code's details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| system | yes | Classification of the code. | |
| parent | no | Code whose children to list. | |
| node | no | Node id from an earlier listing, for ICD-11 blocks without a code. |
Read the WHO ICD-10/ICD-11 mapping rows for one code, verbatim: to_icd11 for a Polish ICD-10 code, to_icd10 for an ICD-11 code. WHO states no match type, its ICD-10 side is the 2019 edition, not Polish 2008, and ICD-11 is not in force in Poland: treat a row as a lead and confirm the target with get_code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | yes | An ICD-10 PL code for to_icd11, an ICD-11 code for to_icd10. | |
| direction | string | yes | Which WHO tables to read. |
Get one JGP group from the catalog in force on service_date: name, product code, base points per column, scopes, the act and release, the knowledge horizon and its grouping conditions with the directional lists they name. Pass a named list's id and catalog to get_jgp_list for its codes; use compare_jgp_group for changes between dates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | yes | JGP group code, e.g. F72. | |
| service_date | no | Day of care, YYYY-MM-DD; picks the release in force. Default today in Poland. |
List the codes of one directional diagnosis or procedure list from JGP attachment 9, one page at a time. Take list_id from conditions.lists[].id and catalog from group.catalog of a get_jgp_group answer, with the same service_date. For the groups that name a given code, use get_code instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List id that get_jgp_group names. |
| catalog | no | Catalog that get_jgp_group names with the list. | |
| page | integer | no | Page, from 1. |
| service_date | no | Day of care, YYYY-MM-DD; picks the release in force. Default today in Poland. |
Browse the JGP catalog in force on service_date: without catalog and section, the sections of catalogs 1a and 1ae with group counts; with both, that section's groups and base points. Find a group by words with search_codes; open one with get_jgp_group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| catalog | no | Catalog of the section; omit with section for the index. | |
| section | no | Section number from the index. | |
| service_date | no | Day of care, YYYY-MM-DD; picks the release in force. Default today in Poland. |
Compare one JGP group between the catalogs in force on two service dates: act, release, name, base points, scopes and condition list names on each side, plus the fields that changed. Use get_jgp_group for the full conditions on one date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | yes | JGP group code, e.g. F72. | |
| before_date | string | yes | Earlier day of care, YYYY-MM-DD. |
| after_date | string | yes | Later day of care, YYYY-MM-DD. |
List the values a group_case stay needs: ward specialty codes (part VIII of a department code; hospital wards 4000-4951, or every section with wards="all") and discharge modes, each with its legal act, plus hospitalization types and product reporting values. Call it before building the case for group_case.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wards | string | no | hospital: ward codes 4000-4951; all: every section. |
Group one anonymised hospital stay with the Minos Gruper (JGP SZP, supported rule subset): candidate groups with reasons, ranking, base and final points, preparation and limitations. Build case from get_case_dictionaries and codes confirmed with get_code. Send clinical facts only, never names, PESEL or addresses; nothing is stored. Reference, not an NFZ decision.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case | object | yes | The anonymised stay; get_case_dictionaries lists accepted values. |
| service_date | no | Day of care for the catalog, YYYY-MM-DD. Default the discharge day. | |
| reporting_month | no | Reporting month, YYYY-MM-DD (day ignored). Default the service month. | |
| declared_modifiers | array | no | Tariff modifier symbols the provider declares; unapplied ones are listed. |
| detail | string | no | trace adds the full routing trace. |
Show what a watched publisher lists now, as Minos last observed it: RSK resources and files, BAW NFZ orders and attachments, or NFZ dictionaries and notices, with versions and dates. Reads Minos's last snapshot and never calls the publisher. Compare with get_service_info to see whether Minos serves the newest release.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | rsk: RSK resources; baw: NFZ orders; nfz: NFZ dictionaries and notices. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Minos Health or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest5358bedc01d36b53f028e1d4f90570ec2edd69761d821ad5074da3afc552ba09
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_service_info | no tags | |
| search_codes | no tags | |
| get_code | no tags | |
| browse_codes | untrusted-input | untrusted-input: keyword "browse" |
| map_icd10_icd11 | no tags | |
| get_jgp_group | no tags | |
| get_jgp_list | no tags | |
| browse_jgp_catalog | untrusted-input | untrusted-input: keyword "browse" |
| compare_jgp_group | no tags | |
| get_case_dictionaries | no tags | |
| group_case | no tags | |
| get_source_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest5358bedc01d36b53
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Minos Health can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.