Model Context Protocol

Healthcare Pricing MCP Server for AI

Connect Claude and other AI assistants to source-labeled hospital pricing, provider directories, procedure code lookups, and reviewed correction workflows through MCP.

Get started View tools

Loa Care is a healthcare pricing MCP provider. Its remote server is published in the official MCP Registry as io.github.aanari/loacare-healthcare-pricing. The registry lists version 1.0.0 as active and latest, with https://www.loacare.com/api/mcp as its streamable HTTP endpoint. Public server metadata and integration notes are maintained in the Loa Healthcare Pricing repository. The independent MCP Server Hub directory listing provides another public reference for the same hosted server. The independent Glama connector record publishes protocol health and the discovered tool catalog.

The Loa Care MCP server (loacare) is a remote Model Context Protocol server that gives AI assistants like Anthropic's Claude access to U.S. healthcare pricing data sourced from hospital Machine Readable Files (MRFs), public provider identity records, and Loa-reviewed provider corrections. It provides 12 tools for searching medical procedure codes, comparing nearby hospital prices, finding healthcare providers, resolving Loa entity profiles and prices with provenance, explaining source labels, and submitting reviewed entity corrections. Lookup results contain healthcare pricing and provider information.

12 tools

Search codes, compare nearby prices, explain price sources, and submit reviewed corrections.

Source-labeled data

Prices identify Published MRF data, Loa Verified Provider Price overlays, and caveats.

No sign-in to start

Lookup tools work without an account. Sign in to submit provider updates.

Getting started

Server endpoint

https://www.loacare.com/api/mcp

Connect from Claude Desktop

Add the following to your Claude Desktop configuration file:

{ "mcpServers": { "loacare": { "url": "https://www.loacare.com/api/mcp" } } }

Authentication

Read-only lookup tools work without authentication. OAuth 2.1 is required for submit_entity_update_request, and raises limits for every tool.

Resource metadata:https://www.loacare.com/.well-known/oauth-protected-resource

Authorization server:https://eknkfyyjqxuvgdzocccu.supabase.co/auth/v1

Scopes:openid email profile

Token header:Authorization: Bearer <token>

Rate limits

Tier	Limit	Tools available
No sign-in	Daily limit	Read-only lookup tools
Authenticated	Monthly limit	Read-only lookup tools
Linked provider	Higher monthly limit	Higher limits and verified affiliation signals for `submit_entity_update_request` requests

Tools

Most tools are read-only and return JSON with provenance. The only mutating tool is submit_entity_update_request, which creates a reviewed correction request and captures verification evidence.

search_cpt_codes

Search for medical procedure codes (CPT/HCPCS) by name, description, or code number.

Parameters

Name	Type	Required	Description
query	string	Yes	Procedure name, medical term, or CPT code number (e.g. "knee MRI", "99213")
specialty	string	No	Filter by medical specialty (e.g. "cardiology")
category	string	No	"evaluation_management", "laboratory", "radiology", "surgery", or "preventive"
limit	number	No	Max results (default 10, max 25)

Example

{ "query": "knee MRI", "specialty": "orthopedics" }

search_providers

Search for healthcare providers by name, specialty, or location. Legacy provider lookup may use public NPI data; Loa entity tools use the reviewed runtime layer.

Parameters

Name	Type	Required	Description
specialty	string	No	Medical specialty (e.g. "Cardiology")
location	object	No	{ city, state, zip_code } - any combination
name	string	No	Provider name to search for
limit	number	No	Max results (default 20, max 50)

Example

{ "specialty": "Dermatology", "location": { "state": "CA", "zip_code": "90210" } }

get_pricing_estimate

Get estimated procedure costs from published hospital price transparency rows and source-labeled Loa data.

Parameters

Name	Type	Required	Description
procedure_codes	string[]	Yes	CPT codes to price (e.g. ["99213", "85025"]), max 10
zip_code	string	No	ZIP code for regional pricing (defaults to national average)

Example

{ "procedure_codes": ["99213", "85025"], "zip_code": "10001" }

get_market_pricing

Get market average pricing including cash pay and insurance rates from hospital price transparency files.

Parameters

Name	Type	Required	Description
cpt_codes	string[]	Yes	CPT codes to look up (max 10)
state	string	No	State for regional pricing (e.g. "CA"). Falls back to national average.
zip_code	string	No	ZIP code for location context

Example

{ "cpt_codes": ["99213", "93000"], "state": "NY" }

search_hospitals

Search for hospitals by location or name. Returns Loa hospital IDs, addresses, and contact details.

Parameters

Name	Type	Required	Description
state	string	No	State code (e.g. "CA", "NY")
city	string	No	City name
zip_code	string	No	ZIP code
name	string	No	Hospital name to search for
limit	number	No	Max results (default 20, max 50)

Example

{ "state": "NY", "city": "Brooklyn" }

get_hospital_pricing

Get source-labeled hospital pricing, including Published MRF rates and Loa Verified Provider Price overlays when available.

Parameters

Name	Type	Required	Description
hospital_ids	string[]	Yes	Hospital IDs from search_hospitals results (max 10)
cpt_codes	string[]	Yes	CPT procedure codes to look up pricing for (max 10)

Example

{ "hospital_ids": ["hosp_abc123"], "cpt_codes": ["99213"] }

compare_local_prices

Compare hospitals near a ZIP code for one procedure, ranked by cash price or insurer rate, with distance and what each price includes.

Parameters

Name	Type	Required	Description
cpt_code	string	Yes	One CPT or HCPCS code
zip_code	string	Yes	5-digit ZIP code
radius_miles	number	No	Search radius (default 25, max 100)
insurer	string	No	Insurance company name, e.g. "Aetna"
sort	string	No	"price" (default) or "distance"

Example

{ "cpt_code": "73721", "zip_code": "77030", "insurer": "Aetna" }

search_entities

Search Loa runtime hospital and provider entity pages by name, state, or entity type.

Parameters

Name	Type	Required	Description
query	string	No	Hospital or provider name
entity_type	string	No	"hospital" or "provider"
state	string	No	Two-letter state code
limit	number	No	Max results (default 20, max 50)

Example

{ "query": "Alaska Regional", "entity_type": "hospital" }

get_entity_profile

Get one Loa hospital or provider profile by exact slug or entity_pages.id, including field-level provenance.

Parameters

Name	Type	Required	Description
slug_or_id	string	Yes	Exact entity slug or entity_pages.id from search_entities
entity_type	string	No	Optional "hospital" or "provider" disambiguation

Example

{ "slug_or_id": "alaska-regional-hospital-anchorage-ak" }

get_entity_prices

Return source-labeled prices for one Loa hospital or provider entity, including Published MRF Price and Loa Verified Provider Price labels when available.

Parameters

Name	Type	Required	Description
slug	string	Yes	Exact Loa entity slug
cpt_codes	string[]	No	Optional CPT filter, max 25
limit	number	No	Max prices (default 50, max 100)

Example

{ "slug": "alaska-regional-hospital-anchorage-ak", "cpt_codes": ["11600"] }

explain_price_sources

Explain source labels, confidence, caveats, and comparable MRF prices behind prices for one Loa entity.

Parameters

Name	Type	Required	Description
slug	string	Yes	Exact Loa entity slug
cpt_codes	string[]	No	Optional CPT filter, max 25
limit	number	No	Max prices to inspect (default 50, max 100)

Example

{ "slug": "alaska-regional-hospital-anchorage-ak", "cpt_codes": ["11600"] }

submit_entity_update_request

Sign-in requiredReviewed update

Submit a provider or hospital profile, listing, or price correction for Loa review. This is the only mutating provider/entity MCP tool, and Loa approval is required before public data changes.

Parameters

Name	Type	Required	Description
entity_page_id	string	No	Loa entity_pages.id for the provider or hospital
entity_slug	string	No	Exact Loa entity slug if the id is unavailable
submitter_email	string	Yes	Work email for the submitter
submitter_organization	string	No	Provider, hospital, or agent organization represented by the submitter
request_type	string	Yes	price_update, profile_correction, new_listing, remove_listing, or other
source_urls	string[]	No	Public URLs reviewers can use to verify the change
source_notes	string	No	Short verification notes, source context, or callback instructions
idempotency_key	string	No	Optional stable retry key, 8 to 200 characters
price_items	object[]	No	Optional reviewed price rows

Example

{ "entity_slug": "alaska-regional-hospital-anchorage-ak", "submitter_email": "[email protected]", "submitter_organization": "Example Hospital", "request_type": "profile_correction", "source_urls": ["https://example.com/billing"], "source_notes": "Billing office can verify by email." }

Data and privacy

Lookup tools return healthcare pricing and provider information. Price responses label Published MRF data and Loa Verified Provider Price overlays, and may include a comparable MRF price for reviewed provider submissions. Where available, the update-request tool stores your account ID, contact information, correction details, and evidence for Loa review. Search inputs may contain sensitive information; send procedure terms rather than personal medical histories.

Loa Care's MCP tools only process the specific query parameters you submit and do not request your full conversation history. Details included in tool parameters still reach Loa.

Current MCP events collect operational analytics using pseudonymous account or network-source identifiers. We separately retain structured procedure and location searches, returned providers, response positions, and referral clicks for provider reporting. Raw search text is excluded from new events in these analytics. These controls do not automatically remove older records.

Hospital and provider results include a loacare.com link. When someone opens it, we count the click for that listing and forward them to the provider's booking page, website, or Loa profile.

For full details, see Section 5 of our Privacy Policy. Security vulnerabilities can be reported to [email protected].

Frequently asked questions

What is the Loa Care MCP server?

Loa Care's MCP server is a remote Model Context Protocol integration that lets AI assistants like Claude search medical procedure codes, find healthcare providers, resolve Loa entity profiles, compare source-labeled prices, and submit reviewed corrections.

Is Loa an MCP provider for healthcare pricing?

Yes. Loa publishes a remote healthcare pricing MCP server with an active version 1.0.0 listing in the official MCP Registry. The listing identifies Loa as the website and https://www.loacare.com/api/mcp as the streamable HTTP endpoint. Its public GitHub repository contains the published server metadata and integration documentation.

Where does the pricing data come from?

Pricing data is sourced from hospital Machine Readable Files (MRFs) that U.S. hospitals publish under the federal Hospital Price Transparency Rule, plus Loa-reviewed provider submissions when available. Provider profiles come from public identity records and approved profile corrections. Price tools return provenance and source labels instead of blending submitted and source-file data silently.

Do I need an account to use the MCP tools?

No. Read-only lookup tools work without an account, within a daily limit. Sign in with OAuth for higher limits, and submit_entity_update_request.

Does the MCP server access my conversation history?

No. Loa Care's MCP tools only receive the specific query parameters for each tool call (such as a CPT code or ZIP code). It does not request your full conversation history, but details included in tool parameters reach Loa.

Is any personal health information (PHI) involved?

Lookup results contain healthcare pricing and provider information. Free-text inputs can include personal health details, even without an account. Use concise procedure terms and avoid sending medical histories or identifying details.

Which AI platforms are supported?

The server uses the open Model Context Protocol (MCP) standard and works with any compatible client, including Claude Desktop, Claude.ai, and other MCP-enabled AI applications. The server endpoint is https://www.loacare.com/api/mcp.

Troubleshooting

Connection refused or timeout

Verify the endpoint URL is exactly https://www.loacare.com/api/mcp
Ensure your client supports Streamable HTTP transport (not legacy SSE-only)
Check that outbound HTTPS (port 443) is not blocked by a firewall or proxy

401 Unauthorized

Your OAuth token may have expired — re-authenticate to obtain a fresh token
Ensure the token is sent in the Authorization: Bearer <token> header
If using Claude Desktop, remove and re-add the server to trigger a new OAuth flow

429 Too Many Requests

You've exceeded your rate limit for the current period
Authenticated accounts are metered by monthly usage and tool-specific limits
Wait for the limit to reset or upgrade your plan for increased capacity

Tools not appearing in Claude

In Claude Desktop, restart the app after updating your configuration file
Confirm the mcpServers JSON is valid (no trailing commas, correct braces)
On Claude.ai, check that the MCP integration is enabled in your settings

Empty or unexpected results

Verify the CPT code or search query is valid — use search_cpt_codes to find correct codes first
For pricing tools, not all entities have data for every procedure. Try a different CPT code, broaden the search area, or submit an update request
Provider search requires at least one filter (specialty, location, or name)

Still having issues?

Reach out to [email protected] with the error message and the tool you were calling. For security concerns, contact [email protected].

Ready to get started?

Create a free account for higher rate limits and provider correction requests.

Create free account API docs Healthcare pricing API