Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
InSync 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.
What it does
Use an InSync (Qualifacts) patient portal: reads, file transfer, messages and care requests
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'INSYNC_PORTAL=${INSYNC_PORTAL}' --transport stdio insync-mcp '--' npx -y @chrischall/insync-mcp
# 2 — ask your agent for something these tools do
# insync_list_appointments, insync_get_appointment_calendar, insync_list_medications and 23 more
It needs INSYNC_PORTAL: this reads it from your environment, so export it first.
InSync costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts InSync as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads INSYNC_PORTAL (Your practice's portal, scheme and host only, e.g. https://<practice>intouch.insynchcs.com) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx INSYNC_PORTAL … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'INSYNC_PORTAL=${INSYNC_PORTAL}' --transport stdio insync-mcp '--' npx -y @chrischall/insync-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs settings only you can give it: INSYNC_PORTAL — Your practice's portal, scheme and host only, e.g. https://<practice>intouch.insynchcs.com.. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
26 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the patient’s appointments / visits — upcoming or past — with date,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| when | string | no | Which appointments to list. Default upcoming. |
| page | integer | no | 1-based page number. Default 1. |
| page_size | integer | no | Appointments per page (1–100). Default 20. |
| view | yes | — |
Get the monthly appointment calendar — the day, time slot and label of each
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | no | — | |
| to | no | — | |
| view | yes | — |
List prescriptions / medications on file — drug name, dispense, quantity,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Which medications to list. Default current. |
| view | yes | — |
List the patient’s recorded allergies and their reactions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List the patient’s prescription refill-request history — the rows of the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List who you can send a secure message to (the practice groups, with the group id
No parameter schema on file.
Send a new secure message to a practice group. The practice receives it and it cannot be unsent, so it is confirm-gated: the first call returns a preview and a confirmToken, and only a repeat call with that token sends.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to_group_id | yes | Recipient group id, from insync_list_message_recipients. | |
| subject | yes | Message subject. | |
| body | yes | Message text (plain text). |
Reply to a secure message from your practice. Confirm-gated (preview + confirmToken) and cannot be unsent; an unread message is refused unless allow_mark_read is confirmed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| child_id | yes | TODOChildId of the message, from insync_list_messages. | |
| master_id | yes | TODOMasterId of the message, from insync_list_messages. | |
| body | yes | Reply text (plain text). | |
| subject | no | Subject. Default: the portal’s own "Re: …" subject. | |
| allow_mark_read | boolean | no | Set true ONLY after the user agrees an unread message may be marked read. |
Get the patient dashboard badge counts: unread messages, medications, allergies,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
Get the patient account balance: the amount owed (net due) and any credit balance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List patient intake / consent forms the practice has sent. "pending" (the default) is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | "pending" = awaiting the patient (Status "Sent"); "all" = every form. Default pending. |
| view | yes | — |
List patient satisfaction / outcome surveys the practice has sent, with each survey’s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List documents filed to the patient’s portal account. Use the download tools to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List the files attached to a secure message, by the message’s master id (from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| master_id | string | yes | The message’s master id (TODOMasterId) from insync_list_messages. |
| view | yes | — |
Download one file attached to a secure message. Identify it by the message’s master id
| Parameter | Type | Required | Notes |
|---|---|---|---|
| master_id | string | yes | The message’s master id (TODOMasterId) from insync_list_messages. |
| index | integer | yes | The attachment’s 0-based position from insync_list_attachments. |
| output_dir | string | no | — |
Download a document filed to the patient’s portal account. Identify it by the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder_url | string | yes | The document’s DstFolderURL from insync_list_documents (full view). |
| file_name | string | yes | The document’s FileName from insync_list_documents (full view). |
| output_dir | string | no | — |
List secure messages from your practice — unread, read or sent. Returns sender,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder | string | no | Which folder to list. Default unread. |
| search | string | no | Filter to messages matching this text. |
| has_attachment | boolean | no | When true, list only messages that carry an attachment. |
| archived | boolean | no | When true, list archived messages. |
| page | integer | no | 1-based page number. Default 1. |
| page_size | integer | no | Messages per page (1–100). Default 25. |
| view | yes | — |
Read one secure message in full (subject, sent date, body as plain text, attachment
| Parameter | Type | Required | Notes |
|---|---|---|---|
| child_id | string | yes | TODOChildId of the message, from insync_list_messages. |
| master_id | string | yes | TODOMasterId of the message, from insync_list_messages. |
| allow_mark_read | boolean | no | — |
| view | yes | — |
Get the patient’s demographic profile — name, date of birth, contact details and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | yes | — |
List what a refill request can name: the medications on file that can be refilled
No parameter schema on file.
Request a refill of one or more current medications from your practice. Confirm-gated (preview + confirmToken); the practice receives the request and it cannot be withdrawn here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| medication_ids | array | yes | Medication ids to refill, from insync_get_refill_options. |
| refills | integer | yes | How many refills are needed. |
| pharmacy_name | yes | Pharmacy name. | |
| pharmacy_phone | yes | Pharmacy phone number. | |
| pharmacy_address | string | no | Pharmacy address (optional). |
| reason | string | no | Reason for the refill (optional). |
| provider_id | no | — |
Find open appointment-request slots on a date: the practice’s facilities, the providers
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | yes | The date to look at, YYYY-MM-DD. | |
| facility_id | no | Facility id. Default: your primary facility. | |
| provider_id | no | Provider id. Default: your primary provider. | |
| visit_type_id | no | Narrow the slots to one visit type. |
Request an appointment in an open slot. Confirm-gated (preview + confirmToken); it is a request the practice confirms, and it cannot be withdrawn here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | yes | The slot date, YYYY-MM-DD. | |
| time | yes | The slot time exactly as insync_find_appointment_slots lists it, e.g. "09:00 AM". | |
| provider_id | yes | Provider id, from insync_find_appointment_slots. | |
| facility_id | no | Facility id. Default: your primary facility. | |
| visit_type_id | no | Visit type id, from insync_find_appointment_slots. | |
| comments | string | no | A note for the practice (optional). |
| telemedicine | boolean | no | Ask for a telemedicine (video) visit. Default false. |
Ask the practice to cancel an upcoming appointment, with a reason. Confirm-gated (preview + confirmToken); the practice reviews the request, and it is refused once the cancellation period has passed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| visit_id | yes | The visit id, from insync_list_appointments. | |
| reason | yes | Reason for cancelling (the portal requires one). |
Upload a photo of your insurance card (front, back, or both) to your own InSync profile, from a local JPG/JPEG/PNG file. Writes to the portal and is irreversible, so it is confirm-gated: the first call returns a preview and a confirmToken, and only a repeat call with that token uploads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| side | string | yes | Which side(s) to upload: front, back, or both. |
| front_path | string | no | Local path to the FRONT image (JPG/JPEG/PNG). Required for side front or both. |
| back_path | string | no | Local path to the BACK image (JPG/JPEG/PNG). Required for side back or both. |
Report portal connectivity from whichever transport is live: the server-side credential sign-in, or the browser bridge. Skipped when no credential resolves.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 InSync or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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.
Any signed-in account that does not publish InSync can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.