AdisInsight
Query Springer Nature's drug-pipeline and trial database from an AI agent.
Query US negotiated healthcare rates — hospital, lab, drug, device — plus a payer/provider graph.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Turquoise MCP server queries US healthcare pricing from Claude, ChatGPT or any MCP-compatible agent. It answers what a named insurer pays a named provider for a billing code in a given state, across five service lines, plus a knowledge graph of how payers and providers relate. Six tools, all read-only, behind a paid Turquoise subscription.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
analyze_devices_rates as the example — it appears only with Device Rates access. A missing tool is an entitlement fact, not a bug.prompts/list, so we cannot say whether the server serves any.llms.txt, no docs. host. Everything the vendor says about the tools sits on a single page, and its tool table is a raster image rather than text.No. The connector returns negotiated prices between providers and insurers, not medical records. Turquoise defines its dataset in its Master Service Agreement as publicly available data that it aggregates, and the same agreement bars customers from processing PHI through the platform at all unless they first sign a Business Associate Agreement. Its AI terms separately forbid putting medical or personal information into prompts.
It requires a paid subscription. Turquoise names four qualifying products: Market Intelligence, Contract Intelligence, Precision Contracting, or a historical paid data plan. You also need an account with AskTQ and Clear Rates access — Turquoise's stated test is whether you can already sign in and use AskTQ. The connector authenticates as your existing Turquoise user, so there is no separate signup.
No. Turquoise states plainly that all Turquoise Connector tools are read-only and that an AI tool can query data but never modify anything in your platform account. All six tool names in Anthropic's directory are queries, and Anthropic's own permissions label for the connector is Read. Both sources agree, which is not always the case for connectors labelled this way.
Relationships between healthcare organisations rather than prices. Turquoise describes it as searching and traversing entity relationships across payers, providers, health systems, geographies, service lines, network types and product lines. It supports three operations: searching for entities, listing one entity's relationships, and retrieving relationship data. Use it to resolve which corporate entity you actually mean before pulling rates for it.
Your organisation probably lacks access to that dataset. Turquoise states that the tools you see follow your organisation's data access, and gives the device rates tool as its example — it appears only for organisations with Device Rates. Results are scoped the same way, so query a state or market your subscription covers. Turquoise says a newly granted tool appears within a few minutes.
Use analyze_professional_rates for physician-billed services and analyze_medical_rates for facility-billed ones. Turquoise splits its tools along the US billing divide: professional covers physician groups, urgent care clinics and dialysis centres, while medical covers inpatient and outpatient care at hospitals and ambulatory surgery centres. The same encounter can generate both a facility charge and a professional charge.
No. Turquoise's Master Service Agreement grants a non-exclusive, non-transferable, non-sublicensable right to use its data internally only. It separately bars sublicensing, reselling or time-sharing the data, using it for anyone other than the customer, and building a competing product with it. Turquoise asserts copyright over the compilation and calls the dataset a trade secret.
Probably yes, and Turquoise puts the obligation on you. Its Master Service Agreement has the customer warrant that it holds an American Medical Association licence, or is otherwise permitted, to use CPT and related coding data. The agreement explicitly states the customer is not relying on any licence Turquoise may hold, and waives claims against Turquoise about CPT use.
documentation URL, and the only substantive vendor page on the connector — its tool table is published as a PNG image, transcribed here rather than reproduced) · retrieved 2026-08-19robots.txt and no llms.txt are served on turquoise.health — both return HTTP 404, so no Content-Signal axes are declared and no crawl restriction applies (checked 2026-08-19). No docs. host resolves · retrieved 2026-08-19POST to the endpoint returns HTTP 401 with www-authenticate: Bearer error="invalid_token", resource_metadata="…" · retrieved 2026-08-19Connect Turquoise once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.