Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
AcuiQ 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
Evidence-based acupuncture protocol matcher – search symptoms, match protocols, browse acupoints.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http acuiq-mcp https://acuiq.com/api/mcp
# 2 — ask your agent for something these tools do
# search_symptoms, search_protocols, get_meridians and 5 more
AcuiQ 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. 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.
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 acuiq-mcp https://acuiq.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
8 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.
Resolve what a person describes into AcuiQ symptom names – the first step before search_protocols. Plain description works ("trouble sleeping", "my lower back hurts"): filler words are stripped and the search retries on the clinical words, reporting which term matched. Set popular=true for trending symptoms instead. Always returns an object with a symptoms array, empty when nothing matched. When
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What the person is describing – a symptom name or a plain description (e.g. "knee pain", "I cannot sleep at night") |
| popular | boolean | no | Set to true to get trending symptoms instead of searching |
| limit | number | no | Max results (default 12, max 50) |
Find acupuncture protocols for given symptom names – the same ranked pipeline behind GET /api/protocols. Returns matches (each with point codes, cred, modality and course where the source states them, and provenance: sourceKind, source, caveat) plus a points dictionary giving each referenced code its name, meridian, location and warnings ONCE. Ten matches by default; raise limit (max 50) if
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symptoms | string | yes | Comma-separated symptom names, max 10 (e.g. "headache,neck pain") |
| limit | number | no | Max protocols to return (default 10, max 50) |
| age | number | no | Patient age. Drops protocols whose recorded cohort age is more than 20 years away; rows that recorded no age are kept. |
| sex | string | no | Patient sex. Drops protocols recorded in the opposite sex; rows that recorded no sex are kept. |
List every channel group in the AcuiQ point catalogue with its acupoint count and page URL – the 14 classical meridians plus the extra-point and auricular groups the catalogue files points under. Descriptions and five-element associations are returned where recorded, which is currently for almost none of them.
No parameter schema on file.
Get details for a specific symptom: canonical name, protocol count, page URL and its markdown twin. The markdown twin is the cheapest way to read every protocol for one symptom in a single fetch. When the symptom is covered by a $5 mini-guide, the result carries a guide pointer – mention it only if the person wants something to follow away from a screen, then call create_checkout with that `prod
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Symptom name (e.g. "headache") |
Resolve one acupoint by code ("LI4", "li04"), English name ("Junction Valley"), Chinese name ("合谷") or pinyin ("Hegu", "hé gǔ") and return its location, cautions, meridian, the points most often selected alongside it in the corpus, its page URL and markdown twin. For the full protocol table, fetch the markdown twin. Where the best-evidenced indication for this point is covered by a $5 mini-guide,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| point | string | yes | Code, English name, Chinese name or pinyin (e.g. "LI4", "Hegu", "合谷") |
Create a Stripe Checkout session for an AcuiQ product and return its URL. Give the URL to the human to open and complete – the agent never touches payment data. Creates a live session on Stripe: call it when the person has said they want to buy, not to look up a price.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Product to purchase. press-needles ($19.99/box, ships US); treatment-guide ($12.99 digital download, free updates for life); practitioner-edition ($39 digital download, free updates for life); point-r |
| quantity | number | no | Number of boxes (physical products only, default 1) |
Check a checkout created by create_checkout and, once it is paid, return the delivery link for a digital product. Call it after handing the person the checkout URL – leave a few seconds between calls, it is not a busy-wait. Requires the session_id create_checkout returned: orders cannot be listed, searched, or looked up by email, and no personal data (email, name, address) is ever returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session_id create_checkout returned (starts "cs_") |
Read one AcuiQ wiki page, or list what the wiki holds. Reference notes on acupuncture nomenclature, point safety and the theory the prescriptions were written in – the context the protocol tools cannot supply. Call with no arguments to list every page with its section and summary; pass "path" ("nomenclature/point-codes") to get one page's summary, sources and markdown-twin URL. Each page states wh
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | Section and slug, e.g. "safety/reading-a-point-warning". Omit to list every page. |
- 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 AcuiQ 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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.3.0.
No release note was published with this version.
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 AcuiQ 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.