accueil / serveurs / Dev & Code / io.github.aanari/loacare-healthcare-pricing
io.github.aanari/loacare-healthcare-pricing
serveur MCP (Model Context Protocol) · loacare 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.aanari/loacare-healthcare-pricing est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.aanari/loacare-healthcare-pricing » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 12 outils
- compare_local_prices≈ 1415 tokens
Compare 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.
Paramètres, retour & exemple (6)
Paramètressort· string · optionnel · price | distance
Order by price (default) or distancelimit· integer · optionnel
Maximum hospitals to return (default 10, max 20)insurer· string · optionnel
Insurance company name only, e.g. "Aetna" or "Blue Cross"; no member IDscpt_code· string · requis
One CPT or HCPCS code, e.g. "73721" for a knee MRIzip_code· string · requis
5-digit US ZIP code to search aroundradius_miles· integer · optionnel
Search radius in miles (default 25, max 100)
Exemple d'appel{"name": "compare_local_prices", "arguments": {"cpt_code": "texte", "zip_code": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": [], "query": {}, "options": [], "provenance": {}, "insurer_match": "texte", "price_summary": "texte", "hospitals_with_price": 1, "hospitals_without_price": 1}} - explain_price_sources≈ 695 tokens
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.
Paramètres, retour & exemple (3)
Paramètresslug· string · requis
Exact Loa entity slug from search_entities.limit· number · optionnel
Maximum number of prices to inspect, default 50, max 100.cpt_codes· array · optionnel
Optional CPT codes to explain. If omitted, explains current indexed prices.
Exemple d'appel{"name": "explain_price_sources", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"entity": {}, "caveats": [], "cpt_codes": [], "provenance": {}, "price_count": 1, "source_summary": [], "comparable_mrf_price_count": 1}} - get_entity_prices≈ 1445 tokens
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.
Paramètres, retour & exemple (3)
Paramètresslug· string · requis
Exact Loa entity slug from search_entities or a Loa SEO page.limit· number · optionnel
Maximum number of prices, default 50, max 100.cpt_codes· array · optionnel
Optional CPT codes to filter. If omitted, returns current indexed prices up to the limit.
Exemple d'appel{"name": "get_entity_prices", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "entity": {}, "prices": [], "loa_link": "texte", "provenance": {}}} - get_entity_profile≈ 980 tokens
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.
Paramètres, retour & exemple (2)
Paramètresslug_or_id· string · requis
Exact Loa entity slug or entity_pages.id from search_entities.entity_type· string · optionnel · hospital | provider
Optional disambiguation when slug_or_id is a slug.
Exemple d'appel{"name": "get_entity_profile", "arguments": {"slug_or_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"entity": {}, "loa_link": {}, "provenance": {}, "profile_provenance": {}, "profile_field_provenance": {}}} - get_hospital_pricing≈ 863 tokens
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. 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.
Paramètres, retour & exemple (2)
Paramètrescpt_codes· array · requis
CPT procedure codes to look up pricing forhospital_ids· array · requis
Hospital IDs from search_hospitals results
Exemple d'appel{"name": "get_hospital_pricing", "arguments": {"cpt_codes": [], "hospital_ids": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "pricing": [], "provenance": {}, "services_found": 1, "hospitals_found": 1}} - get_market_pricing≈ 1373 tokens
Preferred 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.
Paramètres, retour & exemple (3)
Paramètresstate· string · optionnel
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 limitation.zip_code· string · optionnel
ZIP code, used only to pick the state when state is omittedcpt_codes· array · requis
CPT codes to look up (e.g. ["99213", "93000"])
Exemple d'appel{"name": "get_market_pricing", "arguments": {"cpt_codes": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"state": "texte", "pricing": [], "provenance": {}}} - get_pricing_estimate≈ 744 tokens
Quick 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.
Paramètres, retour & exemple (2)
Paramètreszip_code· string · optionnel
ZIP code used to pick the state (omit for national figures)procedure_codes· array · requis
CPT procedure codes to price (e.g. ["99213", "85025"])
Exemple d'appel{"name": "get_pricing_estimate", "arguments": {"procedure_codes": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"state": "texte", "zipCode": "texte", "disclaimer": "texte", "procedures": [], "provenance": {}, "limitations": [], "missingCodes": [], "estimatedCost": "texte"}} - search_cpt_codes≈ 568 tokens
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.
Paramètres, retour & exemple (4)
Paramètreslimit· number · optionnel
Maximum number of results (default 10, max 25)query· string · requis
Concise procedure name, medical term, or candidate CPT code; omit personal narratives and identifiers (e.g. "knee MRI", "blood work", "99213")category· string · optionnel
Filter by category: "evaluation_management", "laboratory", "radiology", "surgery", "preventive"specialty· string · optionnel
Filter by medical specialty (e.g. "cardiology", "dermatology")
Exemple d'appel{"name": "search_cpt_codes", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "total": 1, "results": [], "category": "texte", "specialty": "texte", "provenance": {}}} - search_entities≈ 781 tokens
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.
Paramètres, retour & exemple (4)
Paramètreslimit· number · optionnel
Maximum number of results, default 20, max 50.query· string · optionnel
Hospital or provider name to search for.state· string · optionnel
Two-letter state code or full state name, e.g. CA or New York.entity_type· string · optionnel · hospital | provider
Optional filter for hospital or provider entities.
Exemple d'appel{"name": "search_entities", "arguments": {"limit": 1, "query": "texte", "state": "texte", "entity_type": "hospital"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "total": 1, "entities": [], "provenance": {}}} - search_hospitals≈ 704 tokens
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.
Paramètres, retour & exemple (5)
Paramètrescity· string · optionnel
City namename· string · optionnel
Hospital name to search forlimit· number · optionnel
Max results (default 20)state· string · optionnel
Two-letter state code or full state name, e.g. "CA" or "New York".zip_code· string · optionnel
ZIP code
Exemple d'appel{"name": "search_hospitals", "arguments": {"city": "texte", "name": "texte", "limit": 1, "state": "texte", "zip_code": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "total": 1, "hospitals": [], "provenance": {}}} - search_providers≈ 798 tokens
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.
Paramètres, retour & exemple (4)
Paramètresname· string · optionnel
Provider name to search for (e.g. "John Smith")limit· number · optionnel
Max results (default 20)location· object · optionnel
Location to search inspecialty· string · optionnel
Medical specialty (e.g. "Cardiology", "Family Medicine")
Exemple d'appel{"name": "search_providers", "arguments": {"name": "texte", "limit": 1, "location": {}, "specialty": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "total": 1, "providers": [], "provenance": {}}} - submit_entity_update_request≈ 1227 tokens
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.
Paramètres, retour & exemple (16)
Paramètresattestation· string · optionnel · provider_representative | authorized_agent | public_source | other
How the submitter is connected to the submitted evidence.entity_slug· string · optionnel
Exact Loa entity slug if entity_page_id is not available.entity_type· string · optionnel · hospital | provider | unknown
Entity kind for the requested update; use unknown only when it cannot be determined.price_items· array · optionnel
Optional structured price rows proposed for Loa review.source_urls· array · optionnel
Optional public URLs reviewers can use to verify the submitted change.request_type· string · requis · price_update | profile_correction | new_listing | remove_listing | other
Type of reviewed change being requested.source_notes· string · optionnel
Short verification notes, source context, or callback instructions.entity_page_id· string · optionnel
Loa entity_pages.id for the provider or hospital.submitter_name· string · optionnel
Name of the person submitting the request.submitter_role· string · optionnel
Submitter role, such as billing manager or authorized agent.idempotency_key· string · optionnel
Optional stable retry key. Loa derives one from the payload if omitted.submitter_email· string · requis
Work email for the submitting representative.submitter_phone· string · optionnel
Optional callback phone number for reviewer follow-up.proposed_changes· object · optionnel
Structured profile or listing fields proposed for Loa review.uploaded_file_url· string · optionnel
Optional public URL for an uploaded evidence file.submitter_organization· string · optionnel
Provider, hospital, or agent organization represented by the submitter.
Exemple d'appel{"name": "submit_entity_update_request", "arguments": {"request_type": "price_update", "submitter_email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "requestId": "texte", "entityPageId": "texte", "reusedExisting": true, "updateRequestId": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».