# Loa Healthcare Pricing (remote · www.loacare.com)

Search source-labeled hospital prices, CPT codes, providers, and healthcare cost estimates.

- Trust score: 76/100 (medium)
- Change this week: +11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.loacare.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/aanari-loacare-healthcare-pricing/api-mcp.md), [page](https://verifymcp.io/servers/aanari-loacare-healthcare-pricing/api-mcp)

## Channel facts

- Endpoint: `https://www.loacare.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1837 tokens (~153/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http aanari-loacare-healthcare-pricing https://www.loacare.com/api/mcp
```

### Codex

```toml
[mcp_servers.aanari-loacare-healthcare-pricing]
url = "https://www.loacare.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aanari-loacare-healthcare-pricing": {
      "type": "remote",
      "url": "https://www.loacare.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aanari-loacare-healthcare-pricing --url https://www.loacare.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aanari-loacare-healthcare-pricing:
    url: "https://www.loacare.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "aanari-loacare-healthcare-pricing": {
      "type": "http",
      "url": "https://www.loacare.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 75, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +5)

- [functional improvement] Tool coverage: 84% → 100%
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-07-27 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (12)

### `search_cpt_codes` (~167 tokens)

CPT Code Search

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.

Input parameters:

- `category` (string): Filter by category: "evaluation_management", "laboratory", "radiology", "surgery", "preventive"
- `limit` (number): Maximum number of results (default 10, max 25)
- `query` (string, required): Search query, procedure name, medical term, or CPT code number (e.g. "knee MRI", "blood work", "99213")
- `specialty` (string): Filter by medical specialty (e.g. "cardiology", "dermatology")

Output parameters:

- `category`
- `provenance` (object)
- `query` (string)
- `results` (array)
- `specialty`
- `total` (number)

### `suggest_procedures` (~101 tokens)

Procedure Suggestions

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 a LOA account.

Input parameters:

- `query` (string, required): Natural language description of the medical need (e.g. "I have a rash on my arm", "need imaging for my lower back pain")

Output parameters:

- `interpretation` (string)
- `needsConfirmationWith` (string)
- `provenance` (object)
- `suggestedCodes` (array)
- `type` (string)

### `search_providers` (~112 tokens)

Provider Search

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.

Input parameters:

- `limit` (number): Max results (default 20)
- `location` (object): Location to search in
- `name` (string): Provider name to search for (e.g. "John Smith")
- `specialty` (string): Medical specialty (e.g. "Cardiology", "Family Medicine")

Output parameters:

- `provenance` (object)
- `providers` (array)
- `query` (object)
- `total` (number)

### `get_pricing_estimate` (~127 tokens)

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 market benchmarks or hospital-specific source-labeled prices, prefer get_market_pricing or get_hospital_pricing.

Input parameters:

- `procedure_codes` (array, required): CPT procedure codes to price (e.g. ["99213", "85025"])
- `zip_code` (string): ZIP code for regional pricing (defaults to national average)

Output parameters:

- `containsHeuristicEstimates` (boolean)
- `disclaimer` (string)
- `estimatedCost` (number)
- `procedures` (array)
- `provenance` (object)
- `zipCode` (string)

### `get_market_pricing` (~148 tokens)

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-hospital rate.

Input parameters:

- `cpt_codes` (array, required): CPT codes to look up (e.g. ["99213", "93000"])
- `state` (string): State for regional pricing (e.g. "CA", "New York"). Unknown states return McpToolInvalidInput. Valid states with no regional data fall back to national averages.
- `zip_code` (string): ZIP code (used with state for location context)

Output parameters:

- `pricing` (array)
- `provenance` (object)
- `state`

### `search_hospitals` (~122 tokens)

Hospital Search

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.

Input parameters:

- `city` (string): City name
- `limit` (number): Max results (default 20)
- `name` (string): Hospital name to search for
- `state` (string): Two-letter state code or full state name, e.g. "CA" or "New York".
- `zip_code` (string): ZIP code

Output parameters:

- `hospitals` (array)
- `provenance` (object)
- `query` (object)
- `total` (number)

### `get_hospital_pricing` (~106 tokens)

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 checking a quoted hospital price against available source rows.

Input parameters:

- `cpt_codes` (array, required): CPT procedure codes to look up pricing for
- `hospital_ids` (array, required): Hospital IDs from search_hospitals results

Output parameters:

- `hospitals_found` (number)
- `pricing` (array)
- `provenance` (object)
- `services_found` (number)
- `total` (number)

### `search_entities` (~117 tokens)

Entity Search

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.

Input parameters:

- `entity_type` (string): Optional filter for hospital or provider entities.
- `limit` (number): Maximum number of results, default 20, max 50.
- `query` (string): Hospital or provider name to search for.
- `state` (string): Two-letter state code or full state name, e.g. CA or New York.

Output parameters:

- `entities` (array)
- `provenance` (object)
- `query` (object)
- `total` (number)

### `get_entity_prices` (~120 tokens)

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.

Input parameters:

- `cpt_codes` (array): Optional CPT codes to filter. If omitted, returns current indexed prices up to the limit.
- `limit` (number): Maximum number of prices, default 50, max 100.
- `slug` (string, required): Exact Loa entity slug from search_entities or a Loa SEO page.

Output parameters:

- `entity` (object)
- `prices` (array)
- `provenance` (object)
- `total` (number)

### `get_entity_profile` (~83 tokens)

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.

Input parameters:

- `entity_type` (string): Optional disambiguation when slug_or_id is a slug.
- `slug_or_id` (string, required): Exact Loa entity slug or entity_pages.id from search_entities.

Output parameters:

- `entity` (object)
- `profile_field_provenance` (object)
- `profile_provenance` (object)
- `provenance` (object)

### `explain_price_sources` (~117 tokens)

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.

Input parameters:

- `cpt_codes` (array): Optional CPT codes to explain. If omitted, explains current indexed prices.
- `limit` (number): Maximum number of prices to inspect, default 50, max 100.
- `slug` (string, required): Exact Loa entity slug from search_entities.

Output parameters:

- `caveats` (array)
- `comparable_mrf_price_count` (number)
- `cpt_codes` (array)
- `entity` (object)
- `price_count` (number)
- `provenance` (object)
- `source_summary` (array)

### `submit_entity_update_request` (~366 tokens)

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 data until Loa approves the request.

Input parameters:

- `attestation` (string): How the submitter is connected to the submitted evidence.
- `entity_page_id` (string): Loa entity_pages.id for the provider or hospital.
- `entity_slug` (string): Exact Loa entity slug if entity_page_id is not available.
- `entity_type` (string): Entity kind for the requested update; use unknown only when it cannot be determined.
- `idempotency_key` (string): Optional stable retry key. Loa derives one from the payload if omitted.
- `price_items` (array): Optional structured price rows proposed for Loa review.
- `proposed_changes` (object): Structured profile or listing fields proposed for Loa review.
- `request_type` (string, required): Type of reviewed change being requested.
- `source_notes` (string): Short verification notes, source context, or callback instructions.
- `source_urls` (array): Optional public URLs reviewers can use to verify the submitted change.
- `submitter_email` (string, required): Work email for the submitting representative.
- `submitter_name` (string): Name of the person submitting the request.
- `submitter_organization` (string): Provider, hospital, or agent organization represented by the submitter.
- `submitter_phone` (string): Optional callback phone number for reviewer follow-up.
- `submitter_role` (string): Submitter role, such as billing manager or authorized agent.
- `uploaded_file_url` (string): Optional public URL for an uploaded evidence file.

Output parameters:

- `entityPageId`
- `requestId` (string)
- `reusedExisting` (boolean)
- `status` (string)
- `updateRequestId` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aanari-loacare-healthcare-pricing/api-mcp#diagnostics

## Score history

- 2026-08-03: 76
- 2026-08-02: 75
- 2026-08-01: 75
- 2026-07-31: 72
- 2026-07-30: 71
- 2026-07-28: 70
- 2026-07-27: 65
- 2026-07-26: 65

## Links

- Remote endpoint: https://www.loacare.com/api/mcp
- Repository: https://github.com/aanari/loacare-healthcare-pricing
- Website: https://www.loacare.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/aanari-loacare-healthcare-pricing/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/aanari-loacare-healthcare-pricing/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/aanari-loacare-healthcare-pricing/api-mcp