Loa Healthcare Pricing

REMOTE · WWW.LOACARE.COM · SCANNED AUG 3

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

Available components

+11 this week 76 76 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security80

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability73

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · www.loacare.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +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.
1 Aug 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +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.
28 Jul 26 +5
- Tool coverage: 84% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.0.1 functional
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 65

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://www.loacare.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=www.loacare.com	CN=YR1,O=Let's Encrypt,C=US	8 Jun 2026	6 Sept 2026	RSA 2048	SHA256-RSA	6cff96bc8f4f369e57b0c7de2cf4895f140
SANs: www.loacare.com
CN=YR1,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC insecure

Validation of www.loacare.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
loacare.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://www.loacare.com/api/mcp	Verified	200
http (plaintext)	http://www.loacare.com/api/mcp	HTTPS enforced	308	https://www.loacare.com/api/mcp

MCP tools — 12 exposed · ~1,686 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

explain_price_sources Explain Price Sources ~117

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 Output Examples

Name	Type	Req	Description
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	yes	Exact Loa entity slug from search_entities.

Name	Type	Req	Description
caveats	array	yes	—
comparable_mrf_price_count	number	yes	—
cpt_codes	array	yes	—
entity	object	yes	—
price_count	number	yes	—
provenance	object	yes	—
source_summary	array	yes	—

No examples provided.

get_entity_prices Entity Prices ~120

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 Output Examples

Name	Type	Req	Description
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	yes	Exact Loa entity slug from search_entities or a Loa SEO page.

Name	Type	Req	Description
entity	object	yes	—
prices	array	yes	—
provenance	object	yes	—
total	number	yes	—

No examples provided.

get_entity_profile Entity Profile ~83

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 Output Examples

Name	Type	Req	Description
entity_type	string	—	Optional disambiguation when slug_or_id is a slug.
slug_or_id	string	yes	Exact Loa entity slug or entity_pages.id from search_entities.

Name	Type	Req	Description
entity	object	yes	—
profile_field_provenance	object	yes	—
profile_provenance	object	yes	—
provenance	object	yes	—

No examples provided.

get_hospital_pricing Hospital Pricing ~106

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 Output Examples

Name	Type	Req	Description
cpt_codes	array	yes	CPT procedure codes to look up pricing for
hospital_ids	array	yes	Hospital IDs from search_hospitals results

Name	Type	Req	Description
hospitals_found	number	yes	—
pricing	array	yes	—
provenance	object	yes	—
services_found	number	yes	—
total	number	yes	—

No examples provided.

get_market_pricing Market Pricing ~148

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 Output Examples

Name	Type	Req	Description
cpt_codes	array	yes	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)

Name	Type	Req	Description
pricing	array	yes	—
provenance	object	yes	—
state	—	yes	—

No examples provided.

get_pricing_estimate Pricing Estimate ~127

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 Output Examples

Name	Type	Req	Description
procedure_codes	array	yes	CPT procedure codes to price (e.g. ["99213", "85025"])
zip_code	string	—	ZIP code for regional pricing (defaults to national average)

Name	Type	Req	Description
containsHeuristicEstimates	boolean	yes	—
disclaimer	string	yes	—
estimatedCost	number	yes	—
procedures	array	yes	—
provenance	object	yes	—
zipCode	string	yes	—

No examples provided.

search_cpt_codes CPT Code Search ~167

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 Output Examples

Name	Type	Req	Description
category	string	—	Filter by category: "evaluation_management", "laboratory", "radiology", "surgery", "preventive"
limit	number	—	Maximum number of results (default 10, max 25)
query	string	yes	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")

Name	Type	Req	Description
category	—	yes	—
provenance	object	yes	—
query	string	yes	—
results	array	yes	—
specialty	—	yes	—
total	number	yes	—

No examples provided.

search_entities Entity Search ~117

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 Output Examples

Name	Type	Req	Description
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.

Name	Type	Req	Description
entities	array	yes	—
provenance	object	yes	—
query	object	yes	—
total	number	yes	—

No examples provided.

search_hospitals Hospital Search ~122

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 Output Examples

Name	Type	Req	Description
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

Name	Type	Req	Description
hospitals	array	yes	—
provenance	object	yes	—
query	object	yes	—
total	number	yes	—

No examples provided.

search_providers Provider Search ~112

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 Output Examples

Name	Type	Req	Description
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")

Name	Type	Req	Description
provenance	object	yes	—
providers	array	yes	—
query	object	yes	—
total	number	yes	—

No examples provided.

submit_entity_update_request Submit Entity Update Request ~366

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 Output Examples

Name	Type	Req	Description
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	yes	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	yes	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.

Name	Type	Req	Description
entityPageId	—	yes	—
requestId	string	yes	—
reusedExisting	boolean	yes	—
status	string	yes	—
updateRequestId	string	yes	—

No examples provided.

suggest_procedures Procedure Suggestions ~101

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 Output Examples

Name	Type	Req	Description
query	string	yes	Natural language description of the medical need (e.g. "I have a rash on my arm", "need imaging for my lower back pain")

Name	Type	Req	Description
interpretation	string	yes	—
needsConfirmationWith	string	yes	—
provenance	object	yes	—
suggestedCodes	array	yes	—
type	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	65
27 Jul	65
28 Jul	70
30 Jul	71
31 Jul	72
1 Aug	75
2 Aug	75
3 Aug	76