Search source-labeled hospital prices, CPT codes, providers, and healthcare cost estimates.
Loa's hosted Model Context Protocol server gives MCP-capable assistants access to source-labeled healthcare pricing, CPT and HCPCS code search, U.S. provider and hospital discovery, and Loa entity profiles.
https://www.loacare.com/api/mcp
The hosted server uses Streamable HTTP. Clients should complete the server's advertised OAuth flow when a tool call requires authentication.
Use this configuration with clients that support remote MCP server URLs:
{
"mcpServers": {
"loacare": {
"url": "https://www.loacare.com/api/mcp"
}
}
}
For clients that require a local command, use the mcp-remote bridge:
{
"mcpServers": {
"loacare": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://www.loacare.com/api/mcp"
]
}
}
}
See the live MCP documentation for current authentication, rate-limit, and troubleshooting guidance.
The server supports workflows for:
The production server currently advertises 12 tools:
search_cpt_codessuggest_proceduressearch_providerssearch_hospitalssearch_entitiesget_entity_profileget_entity_pricesget_hospital_pricingget_market_pricingget_pricing_estimateexplain_price_sourcessubmit_entity_update_requestThe public discovery methods initialize, notifications/initialized, ping, and tools/list can be used without authentication. Tool execution remains OAuth-protected.
Loa returns public healthcare pricing and directory data. It does not require or return Protected Health Information. Pricing responses identify their source labels so clients can distinguish hospital machine-readable-file rows, provider-published prices, market estimates, and reviewed corrections.
server.json is the public metadata submitted to the official MCP Registry under io.github.aanari/loacare-healthcare-pricing.
This repository publishes integration metadata and documentation for Loa's hosted MCP server. The production application source is maintained separately.
This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.