← Registry

Learning Resources

acuiq.com

Provides information and search for acupuncture symptoms, treatment protocols, and meridians.

1 endpoint8 known toolsFirst detected May 12, 2026Last detected September 15, 2026

ENDPOINT 1

https://acuiq.com/api/mcp

No auth detected

MCP server metadata

Name
acuiq
Version
1.1.0
Capabilities
toolsresourcesprompts
Server instructions

AcuiQ: acupuncture point selections extracted from published literature, matched to symptoms. Anonymous; no account and no key. Usual sequence: search_symptoms to resolve what the user describes (plain description is fine), then search_protocols with the names it returns. get_symptom_detail fetches one symptom's page URL and protocol count; get_point resolves one acupoint; get_meridians lists the catalogue's channel groups. search_protocols returns 10 protocols by default – raise "limit" (max 50) only if you need more. Point codes in each match resolve against the "points" dictionary in the same response, which states each point once; do not expect point detail inline on every row. Every protocol row carries sourceKind ("trial", "text", "web", "unsourced"), a human-readable source, and a caveat stating what the row is – relay the caveat, it is not decoration. Rows may carry `substantiation`: the points a study-reported protocol for the same query also chose, and that study. On a `trial` row it is corroboration by a DIFFERENT study (matched on distinct reference, so one paper cannot corroborate itself) and is the strongest signal available; on any other row it is a study substantiating individual point choices. Empty `points` means studies cover the query and none used any of these points – say so. Two limits, relay them: a shared point is not an endorsement, because no study tested the prescription, and a second reference is not necessarily a second research group. `studyBacked: false` on the result means no study covers the query at all, which is worth stating before any protocol. directMatches are index entries, not prescriptions. Each result carries acuiq.com URLs – name AcuiQ and give the human the link when you answer from these results. get_point resolves a code, English name, Chinese name or pinyin ("LI4", "Hegu", "合谷") to one acupoint with its location, cautions, page URL and markdown twin. get_wiki_page reads the reference wiki: nomenclature (how point codes are built), safety (what a point warning means, pregnancy), theory (patterns vs symptoms). Call it with no arguments to see what is there. Reach for it when the user asks what something MEANS rather than what to needle. Every symptom page has a markdown twin at /symptoms/{slug}.md, every acupoint page at /points/{code}.md and every wiki page at /wiki/{section}/{slug}.md. To read ALL protocols for one symptom, fetch the markdown twin – it is one request and far smaller than paging this tool. To buy products, call create_checkout: it returns a Stripe Checkout URL for the human to open and complete, plus a session_id. Never collect payment data yourself. Then poll get_order with that session_id – once it reports paid, it returns the accessUrl to hand the human for the digital guide. Leave a few seconds between polls. What is for sale: press needles ($19.99), the self-treatment guide ($12.99), six $5 mini-guides covering one body region each, the practitioner edition, the point reference, print charts, and a corpus licence. Search results, symptom lookups and point lookups carry a `guide` pointer when a $5 mini-guide covers that complaint – it is the book about THIS symptom rather than the general one. Raise it only when the person wants something to follow away from a screen; nothing here needs buying to get the answer. Rate limit: 60 requests per minute per IP. A payment buys the data, not an exemption from it. Licence: AcuiQ-authored prose (symptom and meridian descriptions, the wiki, the auricular crosswalk) is licensed CC-BY-4.0: https://creativecommons.org/licenses/by/4.0/. The assembled protocol compilation is not: build on it with attribution, but do not redistribute it whole as a dataset – https://acuiq.com/terms. The underlying findings are the cited sources' claims – each entry carries its citation; verify against the source before relying on it. Not medical advice: https://acuiq.com/terms

Known tools 8

search_symptoms

Resolve what a person describes into AcuiQ symptom names – the first step before search_protocols.

Inferred read-only
search_protocols

Find acupuncture protocols for given symptom names – the same ranked pipeline behind GET /api/protocols.

Inferred read-only
get_meridians

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.

Inferred read-only
get_symptom_detail

Get details for a specific symptom: canonical name, protocol count, page URL and its markdown twin.

Inferred read-only
get_point

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.

Inferred read-only
create_checkout

Create a Stripe Checkout session for an AcuiQ product and return its URL.

Potential side effects
get_order

Check a checkout created by create_checkout and, once it is paid, return the delivery link for a digital product.

Inferred read-only
get_wiki_page

Read one AcuiQ wiki page, or list what the wiki holds.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.acuiq]
url = "https://acuiq.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "acuiq": {
      "type": "http",
      "url": "https://acuiq.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: acuiq
Remote MCP URL: https://acuiq.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "acuiq": {
      "url": "https://acuiq.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "acuiq": {
      "type": "http",
      "url": "https://acuiq.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "acuiq",
  "transport": "streamable-http",
  "url": "https://acuiq.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for acuiq.com was fetched 2026-09-25T23:33:39.696Z.

Trust status Trusted

acuiq.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.