Turquoise
by Turquoise
Query US negotiated healthcare rates — hospital, professional, lab, drug and device — from your AI assistant, plus a payer and provider knowledge graph. Six read-only tools, OAuth sign-in, and no patient data: the rates come from regulator-mandated public price files, not medical records.
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.
Connect Turquoise via MCP
https://mcp.turquoise.health/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Turquoise Tools & Capabilities (6)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- It is gated to paying customers. Turquoise names Market Intelligence, Contract Intelligence, Precision Contracting or historical paid data as the qualifying products. There is no free tier for the connector.
- Your tool list is not everyone's tool list. Turquoise states tools follow your organisation's data access and gives
analyze_devices_ratesas the example — it appears only with Device Rates access. A missing tool is an entitlement fact, not a bug. - Results are scoped to your subscription's geography. Turquoise advises querying a state or market your subscription covers, because results follow data access as well.
- Internal use only, and no reselling. Turquoise's MSA grants a non-exclusive, non-transferable, non-sublicensable right to use the data internally, and separately bars sublicensing, reselling, time-sharing, benefiting anyone other than the customer, and building a competing product.
- You need your own CPT licence. The MSA has the customer warrant it holds an AMA licence for CPT and related coding data, states the customer is not relying on any licence Turquoise holds, and waives claims against Turquoise on that point.
- The data is a derived estimate, not a contract. Turquoise publishes a five-level rate score in which only the top level is confirmed by both payer and hospital postings, and states that scores of 1 and 0 are omitted when data is incomplete. Its MSA disclaims all warranties as to accuracy, completeness or legality of the data, and states pricing information is informational only.
- No PHI without a BAA. Turquoise's MSA prohibits processing Protected Health Information through the Service unless a Business Associate Agreement is executed first, and its AI terms prohibit putting personal or medical information into prompts.
- Outputs go to a third-party model. Turquoise's AI Supplemental Terms state its AI tools use third-party large language models, that those services are outside Turquoise's control, and that the customer uses the output at its own risk. Those terms govern Turquoise's own AI features; an MCP client adds a model of your choosing on top.
- We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas and no safety annotations were readable. Tool descriptions and the read-only classification are Turquoise's.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names for this connector, and the gated endpoint blocked our own
prompts/list, so we cannot say whether the server serves any. - The documentation is one blog post. Turquoise publishes no developer docs site for the connector that we could find — no
llms.txt, nodocs.host. Everything the vendor says about the tools sits on a single page, and its tool table is a raster image rather than text.
Frequently asked questions
Does the Turquoise MCP server expose patient data or PHI?
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.
Is the Turquoise connector free, or do you need a paid subscription?
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.
Can the Turquoise MCP server change anything in my account?
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.
What does the explore_knowledge_graph tool actually return?
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.
Why does one of the rate tools not appear in my AI assistant?
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.
Which Turquoise tool should I use for a physician rate versus a hospital rate?
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.
Can I resell or republish rate data retrieved through the Turquoise MCP server?
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.
Do I need my own AMA licence to use CPT codes with this connector?
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.
Sources
- Guide to the Turquoise Connector (MCP) — https://turquoise.health/resources/blog/guide-to-the-turquoise-connector-mcp (fetched 2026-08-19; the directory's
documentationURL, 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-19 - Turquoise Clear Rates data — https://turquoise.health/platform/clear-rates-and-data-assets (fetched 2026-08-19) · retrieved 2026-08-19
- Turquoise Master Service Agreement — https://turquoise.health/legal/master-service-agreement (fetched 2026-08-19; sections 3.2 PHI, 3.4 usage restrictions, 3.5 data restrictions, 7.3 CPT licence, 7.4 disclaimer) · retrieved 2026-08-19
- Turquoise AI Supplemental Terms and Conditions — https://turquoise.health/legal/ai-supplemental-terms-and-conditions (fetched 2026-08-19; last updated by Turquoise 2024-03-06) · retrieved 2026-08-19
- Turquoise Privacy Policy — https://turquoise.health/legal/privacy-policy (fetched 2026-08-19) · retrieved 2026-08-19
- Turquoise sitemap index — https://turquoise.health/sitemap.xml and https://turquoise.health/resources/sitemap.xml (fetched 2026-08-19; used to confirm the legal-document URLs rather than guessing them) · retrieved 2026-08-19
- No
robots.txtand nollms.txtare served onturquoise.health— both return HTTP 404, so noContent-Signalaxes are declared and no crawl restriction applies (checked 2026-08-19). Nodocs.host resolves · retrieved 2026-08-19 - Live RFC 9728 protected-resource descriptor — https://mcp.turquoise.health/.well-known/oauth-protected-resource/mcp (fetched 2026-08-19; the root and path-insert forms both return 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://mcp.turquoise.health/.well-known/oauth-authorization-server (fetched 2026-08-19) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19:
POSTto the endpoint returns HTTP 401 withwww-authenticate: Bearer error="invalid_token", resource_metadata="…"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/78e4613c-7869-4be4-b58f-3794060c704e (snapshot 2026-08-16) · retrieved 2026-08-16
- Turquoise support — mailto:ai@turquoise.health
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Healthcare
- Developer
- Turquoise
- Tools
- 6
- Domain
- mcp.turquoise.health
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.