Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Loa Healthcare Pricing

REMOTE · WWW.LOACARE.COM

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

Available components

0 this week 85 Trust /100

Last scanned (17 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 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 → Why this is hard to 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2980 tokens (~248/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “compare_local_prices” rewrote its description, which is the text the model reads security
    • Tool “get_hospital_pricing” rewrote its description, which is the text the model reads security
    • Tool “get_market_pricing” rewrote its description, which is the text the model reads security
    • Tool “get_pricing_estimate” rewrote its description, which is the text the model reads security
    • “get_hospital_pricing” added an optional parameter “offset” cosmetic
    • “get_hospital_pricing” added an optional parameter “price_limit” cosmetic
    • “get_hospital_pricing” added an optional parameter “price_offset” cosmetic
    • “compare_local_prices” reworded the description of “sort” cosmetic
  • 14 Nov 26 +1
    • Stability: fail → pass ▲ security
  • 13 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “compare_local_prices” rewrote its description, which is the text the model reads security
    • Tool “get_market_pricing” rewrote its description, which is the text the model reads security
    • “compare_local_prices” reworded the description of “deductible_met” cosmetic
    • “compare_local_prices” reworded the description of “sort” cosmetic
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 92.

  • 10 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 88.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 92.

  • 8 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 88.

  • 6 Nov 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
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 21 Nov 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=loacare.com CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 fcaf5bd88483e2350ec0c32ec174a2c2
SANs: loacare.com, *.loacare.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.loacare.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
loacare.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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 301 https://www.loacare.com/api/mcp
MCP tools · 12 exposed · ~2,022 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_local_prices ~278

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Compare published amounts near a ZIP for a code from search_cpt_codes, by price or distance. Lead with the lowest published cash amount, matching insurer rates and conditional verdict. Preserve exact prices, fee scope, extraction/review dates and caveats, including unknown source dates. Older prices remain available. These are not confirmed equivalent services, current quotes or personal out-of-pocket costs. Do not send patient identifiers.

NameTypeReqDescription
cpt_codestringyesOne CPT or HCPCS code, e.g. "73721" for a knee MRI
deductible_metstring–Optional legacy input; does not establish personal insurance costs
insurerstring–Insurance company name only, e.g. "Aetna" or "Blue Cross"; no member IDs
limitinteger–Maximum hospitals to return (default 10, max 20)
radius_milesinteger–Search radius in miles (default 25, max 100)
sortstring–Order by lowest published amount (default) or distance; missing matching amounts sort last when ordering by price
zip_codestringyes5-digit US ZIP code to search around
NameTypeReqDescription
answerobjectyes–
comparison_statusstringyes–
hospitals_with_pricenumberyes–
hospitals_without_pricenumberyes–
insurer_match–yes–
notesarrayyes–
optionsarrayyes–
price_summary–yes–
provenanceobjectyes–
queryobjectyes–

No examples provided.

explain_price_sources ~135

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Explain only the returned source labels, counts, confidence, and caveats. Separate available prices from unavailable placeholders; if none are available, say so without inventing prices or source categories.

NameTypeReqDescription
cpt_codesarray–Optional CPT codes to explain. If omitted, explains current indexed prices.
limitnumber–Maximum number of prices to inspect, default 50, max 100.
slugstringyesExact Loa entity slug from search_entities.
NameTypeReqDescription
available_price_countnumberyesRows with a usable price; excludes unavailable placeholders.
caveatsarrayyes–
comparable_mrf_price_countnumberyes–
cpt_codesarrayyes–
entityobjectyes–
price_countnumberyesTotal resolver rows, including unavailable placeholders.
provenanceobjectyes–
source_summaryarrayyes–
unavailable_price_countnumberyesRows without a usable price; not evidence of a published or verified price.

No examples provided.

get_entity_prices ~133

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Get source-labeled prices by Loa listing slug; use search_entities to resolve it first. Missing CPT prices return explicit unavailable rows.

NameTypeReqDescription
cpt_codesarray–Optional CPT codes to filter. If omitted, returns current indexed prices up to the limit.
limitnumber–Maximum number of prices, default 50, max 100.
slugstringyesExact Loa entity slug from search_entities or a Loa SEO page.
NameTypeReqDescription
entityobjectyes–
loa_link–yes–
pricesarrayyes–
provenanceobjectyes–
totalnumberyes–

No examples provided.

get_entity_profile ~107

Get a hospital or provider profile by exact Loa slug or ID, with field provenance. On request, offer correction_url for corrections plus optional affiliation verification, or claim_url for affiliation only. Both forms allow intake without an account; dashboard access requires verification. Use the exact loa_link.label.

NameTypeReqDescription
entity_typestring–Optional disambiguation when slug_or_id is a slug.
slug_or_idstringyesExact Loa entity slug or entity_pages.id from search_entities.
NameTypeReqDescription
entityobjectyes–
loa_linkobjectyesShare this returned URL with its exact label. A website action redirects to the provider website; only a profile action opens a Loa listing. Do not infer the destination from the loacare.com domain.
profile_field_provenanceobjectyes–
profile_provenanceobjectyes–
provenanceobjectyes–
provider_actions–yes–

No examples provided.

get_hospital_pricing ~194

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Get source-labeled Published MRF prices and Loa-reviewed provider price overlays for named hospitals and CPT codes. Cash is self-pay, list is the gross charge before discounts, and insurer rates are not personal out-of-pocket costs; missing prices are null.

NameTypeReqDescription
cpt_codesarrayyesCPT procedure codes to look up pricing for
hospital_idsarrayyesHospital IDs from search_hospitals results
offsetinteger–Service page offset; use returned next_offset with the same hospitals and codes.
price_limitinteger–Observations per service, default 3, maximum 5.
price_offsetinteger–Observation offset within each service; narrow to one hospital/code and use next_price_offset for more rows.
NameTypeReqDescription
hospitals_foundnumberyes–
next_offset–yes–
notesarrayyes–
offsetnumberyes–
pricingarrayyes–
provenanceobjectyes–
returnednumberyes–
services_foundnumberyes–
totalnumberyes–

No examples provided.

get_market_pricing ~193

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Compare state or national benchmarks of published code-level cash, list and insurer amounts; each hospital counts once. Show medians, ranges, extraction dates and limitations. Fees and settings may differ; these are not complete-care totals or current quotes. Do not fill insufficient_data gaps.

NameTypeReqDescription
cpt_codesarrayyesCPT codes to look up (e.g. ["99213", "93000"])
statestring–State for regional pricing (e.g. "CA", "New York"). Unknown states return McpToolInvalidInput. When fewer than 5 hospitals in the state published a price, national figures are returned with a limitat…
zip_codestring–ZIP code, used only to pick the state when state is omitted
NameTypeReqDescription
pricingarrayyes–
provenanceobjectyes–
state–yes–

No examples provided.

get_pricing_estimate ~165

U.S. care only, for users anywhere. For non-U.S. care, explain coverage without calling this tool or substituting U.S. prices. Estimate median cash prices and typical ranges (25th–75th percentile) for CPT codes, statewide by ZIP or nationally. Show extraction dates and scope limitations. Report missingCodes and insufficient_data without inventing prices; never sum unrelated code medians into a care total. Use get_market_pricing for insurer benchmarks or get_hospital_pricing for named hospitals.

NameTypeReqDescription
procedure_codesarrayyesCPT procedure codes to price (e.g. ["99213", "85025"])
zip_codestring–U.S. ZIP code used to pick the state (omit only for U.S. national figures)
NameTypeReqDescription
disclaimerstringyes–
estimatedCost–yes–
limitationsarrayyes–
missingCodesarrayyes–
proceduresarrayyes–
provenanceobjectyes–
state–yes–
zipCode–yes–

No examples provided.

search_cpt_codes ~147

Find procedures by everyday name or billing code. Follow decision: clarify important variants before pricing; never choose a clinical default.

NameTypeReqDescription
categorystring–Filter by category: "evaluation_management", "laboratory", "radiology", "surgery", "preventive"
limitnumber–Maximum number of results (default 10, max 25)
querystringyesConcise procedure name, medical term, or candidate CPT code; omit personal narratives and identifiers (e.g. "knee MRI", "blood work", "99213")
specialtystring–Filter by medical specialty (e.g. "cardiology", "dermatology")
NameTypeReqDescription
availability_scopestringyes–
category–yes–
coveragestringyes–
decisionobjectyes–
pricing_codesarrayyes–
provenanceobjectyes–
querystringyes–
related_chargesarrayyes–
resultsarrayyes–
specialty–yes–
suggestionsarrayyes–
totalnumberyes–

No examples provided.

search_entities ~105

Find Loa hospital and provider listings by name or state. Resolve the exact slug before profile, price, or source lookups.

NameTypeReqDescription
entity_typestring–Optional filter for hospital or provider entities.
limitnumber–Maximum number of results, default 20, max 50.
querystring–Hospital or provider name to search for.
statestring–Two-letter state code or full state name, e.g. CA or New York.
NameTypeReqDescription
entitiesarrayyes–
provenanceobjectyes–
queryobjectyes–
totalnumberyes–

No examples provided.

search_hospitals ~102

Find hospitals by name or location, with addresses, contact details, and IDs for get_hospital_pricing.

NameTypeReqDescription
citystring–City name
limitnumber–Max results (default 20)
namestring–Hospital name to search for
statestring–Two-letter state code or full state name, e.g. "CA" or "New York".
zip_codestring–ZIP code
NameTypeReqDescription
hospitalsarrayyes–
provenanceobjectyes–
queryobjectyes–
totalnumberyes–

No examples provided.

search_providers ~98

Find clinicians and healthcare organizations in the CMS NPI Registry by name, specialty, or location. Returns directory details, not prices.

NameTypeReqDescription
limitnumber–Max results (default 20)
locationobject–Location to search in
namestring–Provider name to search for (e.g. "John Smith")
specialtystring–Medical specialty (e.g. "Cardiology", "Family Medicine")
NameTypeReqDescription
provenanceobjectyes–
providersarrayyes–
queryobjectyes–
totalnumberyes–

No examples provided.

submit_entity_update_request ~365

Submit a pending listing or price correction for Loa review. Requires sign-in, not a claimed listing; stores business contact details and public evidence. Patient data is unsupported. Does not publish changes, verify affiliation, or grant dashboard access. Website correction and claim links come from get_entity_profile.

NameTypeReqDescription
attestationstring–How the submitter is connected to the submitted evidence.
entity_page_idstring–Loa entity_pages.id for the provider or hospital.
entity_slugstring–Exact Loa entity slug if entity_page_id is not available.
entity_typestring–Entity kind for the requested update; use unknown only when it cannot be determined.
idempotency_keystring–Optional stable retry key. Loa derives one from the payload if omitted.
price_itemsarray–Optional structured price rows proposed for Loa review.
proposed_changesobject–Structured profile or listing fields proposed for Loa review.
request_typestringyesType of reviewed change being requested.
source_notesstring–Short verification notes, source context, or callback instructions.
source_urlsarray–Optional public URLs reviewers can use to verify the submitted change.
submitter_emailstringyesWork email for the submitting representative.
submitter_namestring–Name of the person submitting the request.
submitter_organizationstring–Provider, hospital, or agent organization represented by the submitter.
submitter_phonestring–Optional callback phone number for reviewer follow-up.
submitter_rolestring–Submitter role, such as billing manager or authorized agent.
uploaded_file_urlstring–Optional public URL for an uploaded evidence file.
NameTypeReqDescription
entityPageId–yes–
requestIdstringyes–
reusedExistingbooleanyes–
statusstringyes–
updateRequestIdstringyes–

No examples provided.

Install

How do I install the Loa Healthcare Pricing MCP server?

Loa Healthcare Pricing is a hosted endpoint at https://www.loacare.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.loacare.com

# add to Claude Code
claude mcp add --transport http aanari-loacare-healthcare-pricing 'https://www.loacare.com/api/mcp'
Common questions

What is the Loa Healthcare Pricing MCP server?

Loa Healthcare Pricing is an MCP server listed in the public MCP registry as io.github.aanari/loacare-healthcare-pricing. Search source-labeled hospital prices, CPT codes, providers, and healthcare cost estimates. This page covers its hosted endpoint (https://www.loacare.com/api/mcp).

Is the Loa Healthcare Pricing MCP server safe to use?

Loa Healthcare Pricing scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Loa Healthcare Pricing MCP server expose?

Loa Healthcare Pricing exposes 12 tools: search_cpt_codes, search_providers, get_pricing_estimate, get_market_pricing, search_hospitals, and 7 more. Their descriptions and schemas cost roughly 2,022 tokens of context every time the server is loaded.

Does the Loa Healthcare Pricing MCP server require authentication?

No. We connected to Loa Healthcare Pricing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Loa Healthcare Pricing MCP server still maintained?

Loa Healthcare Pricing is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Loa Healthcare Pricing MCP server?

VerifyMCP ran 13 checks on Loa Healthcare Pricing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.