# Loa Healthcare Pricing Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Loa Healthcare Pricing

Search hospital prices, CPT codes, and healthcare cost estimates from public price transparency data.

- Record: https://musedirectory.ai/connector/loa-healthcare-pricing
- Category: Health
- Developer: Loa Care (https://www.loacare.com/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 565ms, checked 2026-09-28T08:31:06Z
- Endpoint: https://www.loacare.com/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T03:11:11Z)
- Source: Found in the official MCP Registry (io.github.aanari/loacare-healthcare-pricing) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.aanari%2Floacare-healthcare-pricing

Look up procedure costs at specific hospitals and compare regional pricing. Search by procedure name, CPT code, or medical specialty. Get source-labeled prices from hospital price-transparency files and market benchmarks to estimate out-of-pocket costs before scheduling care.

Example request: "What does an MRI of my knee cost at hospitals near me?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Loa Healthcare Pricing to help me. It is a free service with an MCP server at https://www.loacare.com/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- search_cpt_codes: Canonical code-lookup tool for this server. Search Loa's CPT/HCPCS index using exact codes, clinical terms, or consumer phrases. Use this first when the user does not already know the CPT code, before calling pricing tools.
- suggest_procedures: Advisory helper that suggests likely CPT codes from a plain-English medical need. Uses Loa heuristics plus AI and is not authoritative or diagnostic. Use only when the user cannot name the procedure, then confirm candidates with search_cpt_codes before pricing them. Requires sign
- search_providers: Search public CMS NPI Registry data for clinicians and healthcare organizations by specialty, name, or location. Use returned provenance to understand the registry source and scope. Use this for provider lookup, not pricing.
- get_pricing_estimate: Quick directional estimate for one or more CPT codes. Prefers observed national market pricing derived from hospital price-transparency data, but falls back to a broad CPT-range heuristic when observed pricing is missing. Use this for a fast ballpark total. For source-grounded ma
- get_market_pricing: Preferred benchmark pricing tool. Returns market cash/self-pay and insurance-negotiated price summaries for CPT codes, aggregated from Loa's hospital price-transparency dataset. Use this when the user wants source-grounded regional or national market pricing rather than a single-
- search_hospitals: Search Loa's hospital directory by name or location and return hospital IDs plus address details. Use the returned hospital_ids with get_hospital_pricing to fetch source-labeled Published MRF and reviewed overlay prices.
- get_hospital_pricing: Hospital-specific pricing tool for source-labeled Loa runtime data. Returns source-labeled Published MRF prices and Loa Verified Provider Price overlays for CPT codes, including cash/self-pay and payer-negotiated rates when available. Use this when comparing named hospitals or ch
- search_entities: Search Loa runtime hospital and provider entity pages by name or state. Use this before get_entity_prices when the user names a hospital or provider but does not know the exact Loa slug.
- get_entity_prices: Return source-labeled prices for a Loa hospital or provider entity slug using the shared resolver. Use search_entities first if the slug is unknown. Results include provenance and explicit unavailable rows for requested CPT codes with no current price.
- get_entity_profile: Return one Loa hospital or provider entity profile by exact slug or entity_pages.id. Includes profile-field provenance so agents can distinguish source-file fields from Loa-reviewed overrides.
- explain_price_sources: Explain the source labels, provenance, confidence, and caveats behind Loa prices for one hospital or provider entity. Use this when an agent needs to tell a user why prices are MRF-published, Loa-reviewed, estimated, or unavailable.
- submit_entity_update_request: Submit a profile, listing, or price correction for Loa review without requiring a provider portal. This is the only mutating provider/entity tool. It requires OAuth, captures submitter and source evidence, records linked-provider status when available, and never changes public da

Screening checks:
- MCP handshake: pass (Answered in 318ms)
- Domain against threat feeds (Cloudflare security DNS): pass (www.loacare.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (12 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 541 days ago)
- AI review of purpose and tool behavior: pass (No concerns)