Loa Healthcare Pricing vs Medicare Pricing
A side-by-side look at the Loa Healthcare Pricing and Medicare Pricing MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Loa Healthcare Pricing for biology & bioinformatics work over a hosted endpoint; choose Medicare Pricing for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Loa Healthcare Pricing when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
search_cpt_codes, search_providers, get_pricing_estimate.
Choose Medicare Pricing when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
medicare_physician_payment, medicare_lab_rate, medicare_lab_test_lookup.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 8 |
| Full listing | View Loa Healthcare Pricing | View Medicare Pricing |
Tools & capabilities
Loa Healthcare Pricing tools 12
search_cpt_codesCanonical 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.search_providersSearch 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_estimateQuick cash-price ballpark for one or more CPT codes, using the median cash price across hospitals in the state (from zip_code) or nationally. priceRange is the typical range (25th to 75th percentile of hospitals). Codes without enough data return insufficient_data and are listed in missingCodes; the total is null unless every code has data. Never fill gaps with your own estimate. For insurer rates or hospital-specific prices, use get_market_pricing or get_hospital_pricing.get_market_pricingPreferred benchmark pricing tool. Returns hospital-level market statistics for CPT codes from Loa's published hospital price-transparency data: cash/self-pay prices, list prices (gross charges before discounts), overall insurer-negotiated rates, and rates for the most common insurers. Each hospital counts once. Lead with the median and the p25-p75 range rather than min or max. Figures are statewide or national, never local to a ZIP code. When status is insufficient_data, say Loa doesn't have enough data instead of estimating, and always relay the limitations. Negotiated rates are not out-of-pocket costs.search_hospitalsSearch 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_pricingHospital-specific pricing tool for source-labeled Loa runtime data. Returns source-labeled Published MRF prices and Loa Verified Provider Price overlays for CPT codes. cash_price is the cash/self-pay price, list_price is the gross charge before discounts (most patients pay less), and insurance_prices are payer-negotiated rates for the named plan, not out-of-pocket costs. Any of these can be null when the hospital did not publish that price. Use this when comparing named hospitals or checking a quoted hospital price against available source rows.compare_local_pricesCompare hospitals near a ZIP code for one procedure code, ranked by price (or distance) only. Without insurer, price is the published cash (self-pay) price. With insurer, price is that insurer's negotiated rate, which is not the patient's out-of-pocket cost. Each option says what the price includes, its source and date, distance in miles, and loa_link for booking or contact. Every priced hospital in the radius is ranked before limit applies. Hospitals with no price for the code are counted in hospitals_without_price; hospitals without a matching cash price or insurer rate are listed last with price null. Get the code from search_cpt_codes first. Do not send member IDs or other personal details.search_entitiesSearch 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_pricesReturn 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_profileReturn 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_sourcesExplain 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_requestSubmit 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 data until Loa approves the request.
Medicare Pricing tools 8
medicare_physician_payment"How much does Medicare pay for 99213 in Los Angeles?" — RVUs and dollars, locality-adjusted.medicare_lab_rate"What does a comprehensive metabolic panel reimburse?" — national CLFS rate.medicare_lab_test_lookup"What does Medicare pay for Signatera, and which MolDX LCD applies?" — brand name → PLA code, current CLFS rate, and the MolDX LCDs/articles for the test's category.medicare_dmepos_rate"How much does Medicare pay for a CPAP machine (E0601) in Texas?" — state-priced, rural vs non-rural.medicare_code_units_limit"How many units of this code will they pay for in one day?" — NCCI MUE.check_code_pair"Can I bill 00142 and 64474 together?" — NCCI PTP edit + modifier indicator for a code pair.explain_ncci_edit"What is bundled into (or bundles into) this code?" — every recorded PTP edit for one code.medicare_pricing_coverageWhich vintages are loaded, including the PTP baseline vintage.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Loa Healthcare Pricing
{
"mcpServers": {
"loa-healthcare-pricing-2": {
"url": "https://www.loacare.com/api/mcp"
}
}
}
Medicare Pricing
{
"mcpServers": {
"medicare-pricing": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-medicare-pricing"
]
}
}
}
Frequently asked questions
Loa Healthcare Pricing is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Medicare Pricing belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Loa Healthcare Pricing for biology & bioinformatics work and Medicare Pricing for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Loa Healthcare Pricing has no declared pricing — check the project's own site. Auth: oauth 2.0. Medicare Pricing has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add loa-healthcare-pricing-2 and medicare-pricing as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Loa Healthcare Pricing has a quality signal of 57/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Medicare Pricing has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.