{"id":"com.medigami/mcp","slug":"com-medigami-mcp","title":"Medigami","description":"Medigami: medical bill error scan, denial decoding, appeal deadlines, hospital price lookup","version":"1.0.0","publisher":{"kind":"domain","id":"medigami.com","label":"medigami.com","url":"https://medigami.com"},"website":"https://medigami.com/mcp","repository":"","remotes":[{"type":"streamable-http","url":"https://mcp.medigami.com/public/mcp"}],"packages":[],"published":"2026-09-07","updated":"2026-09-07","status":"online","auth":"","latency_ms":1044,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"scan_bill_for_errors","title":"","description":"Scan a medical bill or EOB text for errors: duplicate charges, CPT unbundling, upcoding, facility-fee overcharges. Returns flagged anomalies with estimated dollar impact and a total recovery estimate.\n\nPHI WARNING: bill text typically contains PHI (patient name, DOB, MRN, insurer ID). Medigami runs a server-side PHI redactor before any downstream LLM call when scan_bill is invoked from the public ","read_only":false},{"name":"generate_appeal_letter","title":"","description":"Generate a legally-grounded insurance appeal letter for a denied claim. Returns the letter as a template with [PATIENT NAME] and [PROVIDER NAME] placeholders (structured-only PHI posture). Includes legal citations, recommended attachments, and appeal-deadline calendar.\n\nWHEN TO USE: User has a specific claim denied and wants a drafted appeal letter. Requires insurer, denial_reason (CARC code), cpt","read_only":false},{"name":"optimize_prescription","title":"","description":"Find the lowest-cost path for a prescription: generics, biosimilars, GoodRx coupons, manufacturer assistance, 90-day fills, and mail-order vs retail comparison. Returns ranked options with annual savings vs current copay.\n\nWHEN TO USE: User asks about prescription cost — lowest-price generic, biosimilar, GoodRx coupon, mail-order, manufacturer assistance, or 90-day fill options.\n\nWHEN NOT: For ins","read_only":false},{"name":"analyze_glp1_pathways","title":"","description":"Find all access pathways for a GLP-1 drug (Ozempic, Wegovy, Mounjaro, Zepbound) given patient eligibility factors. Ranks pathways by monthly cost, flags prior-authorization rules and step-therapy, and returns the recommended appeal strategy if denial is likely.\n\nWHEN TO USE: User specifically asks about GLP-1 drugs (Ozempic, Wegovy, Mounjaro, Zepbound) — coverage, prior-auth strategy, step-therapy","read_only":false},{"name":"verify_attestation","title":"","description":"Verify an Ed25519-signed Medigami MCP response envelope — confirm a medical-bill / appeal / denial / rate answer came from Medigami and hasn't been tampered with. Input: the signed envelope + a public key (PEM) or expected-fingerprint you pinned out-of-band. Returns {valid, reason, tracking_id, timestamp, exp, public_key_fingerprint} so callers can cite the result as FRE 902(14) self-authenticatin","read_only":false},{"name":"watch_appeal_outcome","title":"","description":"Subscribe to an appeal outcome by tracking_id. Blocks up to `timeout_seconds` (default 300). Returns the outcome payload as soon as it's recorded, or {status: 'timeout'} if nothing resolved within the window — caller re-invokes to keep watching. Tracking ids are returned by estimate_appeal_success and other Tier 3 moat tools.\n\nWHEN TO USE: Caller wants to subscribe to the outcome of an in-flight a","read_only":false},{"name":"watch_claim_denial","title":"","description":"Subscribe to a claim denial event for a given scan_id. Blocks up to `timeout_seconds`. Returns {status: 'denied', ...} as soon as the payer marks the claim denied in claim_status_history, or {status: 'timeout'} if no denial observed within the window.\n\nWHEN TO USE: Caller wants to stream denial events for a set of claims.\n\nWHEN NOT: One-shot queries.","read_only":false},{"name":"format_citation","title":"","description":"Format an LLM-citable reference to a previously-attested Medigami MCP response. Input: either the full signed envelope that an earlier attested tool returned, OR just a tracking_id. Returns a short citation string, a public verification URL a third party can open to inspect and cryptographically verify the payload, and a long-form attribution block. Use this after any substantive Medigami tool cal","read_only":false},{"name":"submit_denial_letter","title":"","description":"Submit a medical-claim denial letter to the Medigami Denial Common Crawl (public aggregate dataset). Consent-gated — caller must pass consent=true to attest the submission is voluntary. Server-side PHI scrubber runs before any storage; the public aggregate contains only coded fields (insurer_canonical, denial_reason_code, state, cpt_category, dollars_bin, days_to_resolution_bin). Raw text is never","read_only":false},{"name":"verify_mcp_response","title":"","description":"DEPRECATED ALIAS of verify_attestation — kept for backward compatibility with v0.1.7 clients. New code should call verify_attestation directly.\n\nWHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome.\n\nWHEN NOT: For composite workflows use the higher-level tool that calls these internally.","read_only":false},{"name":"format_medigami_citation","title":"","description":"DEPRECATED ALIAS of format_citation — kept for backward compatibility with v0.1.7 clients. New code should call format_citation directly.\n\nWHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome.\n\nWHEN NOT: For composite workflows use the higher-level tool that calls these internally.","read_only":false},{"name":"estimate_appeal_success","title":"","description":"Probability an appeal will be approved, derived from outcome-labeled data weighted by label provenance (IRO determinations, EOB reversals, physician confirmations). Returns probability + 95% CI + sample_size + expected_days_to_resolution + tracking_id. Report the actual outcome later via POST /api/outcomes/record with the same tracking_id to improve future estimates.\n\nWHEN TO USE: User or caller w","read_only":false},{"name":"resolve_denial","title":"","description":"End-to-end denial resolution: returns appeal probability + confidence interval + a drafted letter template grounded in aggregate outcome data + plan-context flags (ERISA, restrictive-adjuster state). One call, one tracking_id. No recovery-financing product is offered by this tool.\n\nWHEN TO USE: Single-shot composite: user has a specific denial and wants scan + estimate + appeal + citation in one c","read_only":false},{"name":"maximize_recovery","title":"","description":"Given a prior scan_id, returns a prioritized action list: anomalies ranked by (expected overcharge x recovery probability), with the next steps to pursue each. Use after scan_bill_for_errors.\n\nWHEN TO USE: User has already run scan_bill_for_errors and wants the anomalies ranked by expected dollar recovery.\n\nWHEN NOT: As a first call — always scan first.","read_only":false},{"name":"explain_appeal_success","title":"","description":"Human-readable rationale for an appeal probability. Returns {probability, tier, recommended_posture, rationale, expected_days_to_resolution, tracking_id} grounded in aggregate outcome rates — not model feature weights. Use this when the caller wants 'why' in plain English alongside the number.\n\nWHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a","read_only":false},{"name":"negotiate_bill_script","title":"","description":"Generate a phone script the user can read when negotiating a medical bill directly with the provider. Combines DP-noised commercial rate benchmarks + the caller's household income + federal charity-care rules (IRS §501(r)) into three negotiation angles: financial assistance, self-pay discount, and itemized-bill coding review. Returns the script + reference-only benchmark range (for the user's own ","read_only":false},{"name":"batch_scan_bills","title":"","description":"Scan multiple medical bills in one call. Returns per-bill anomaly lists + total recovery estimate across the batch. Input is a list of {bill_text, provider?, insurer?} items (max 10 per call). Much faster than serial scan_bill_for_errors when handling a bulk upload.\n\nWHEN TO USE: User has multiple bills or EOBs to review at once (e.g. a family's bills from one visit, or a year of statements).\n\nWHE","read_only":false},{"name":"lookup_icd10","title":"","description":"Look up an ICD-10-CM diagnosis code or search by keyword. Input is either an exact code (e.g. 'E11.21') or a free-text description phrase ('type 2 diabetes with nephropathy'). Returns either the matching code + description or up to 20 candidate matches. Use when a clinical note uses non-standard phrasing and the correct code is needed for billing.\n\nWHEN TO USE: User asks about a specific ICD-10 di","read_only":false},{"name":"lookup_cpt","title":"","description":"Look up a CPT or HCPCS-J code or search by keyword. Covers the most common outpatient billing codes (E/M, preventive, lab, imaging, procedure, cardiology, therapy, behavioral, vaccine, injectable drugs). Note: CPT is a registered trademark of the American Medical Association; full-dataset commercial use requires an AMA license. This tool provides short descriptors for identification in billing-rev","read_only":false},{"name":"lookup_npi","title":"","description":"Look up a provider in the CMS NPPES National Provider Identifier registry. Accepts a 10-digit NPI number OR a provider name (optionally narrowed by 2-char state). Returns up to 20 matches with entity type, specialty, taxonomy code, address, and status. Source: CMS NPPES public API (free, no key required).\n\nWHEN TO USE: User wants to verify a specific provider by NPI number, or find a provider by n","read_only":false},{"name":"verify_dea_authorization","title":"","description":"Validate the format + checksum of a DEA registration number (format: [A-Z][A-Z9][0-9]{7}; public checksum algorithm). Useful as a sanity check on a DEA number you were given (e.g. on a prescription label or a provider's letterhead). Scope note: this tool confirms the number is well-formed — it does NOT verify current registration status or the specific controlled-substance schedule the holder is a","read_only":false},{"name":"lookup_provider_taxonomy","title":"","description":"Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted).\n\nWHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description.\n\nWHEN NOT: For finding a provider by specialty in a re","read_only":false},{"name":"resolve_codes","title":"","description":"[Taxonomy A.1 — baseline response (public data only)] Unified code resolver — free-form query or clinical description → ranked ICD-10-CM, CPT, and HCPCS codes with confidence scores. Use when you need to translate symptoms, procedures, or diagnoses into billable codes without running three separate lookups.\n\nWHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a cod","read_only":false},{"name":"code_conflict_detector","title":"","description":"[Taxonomy A.5 — delegates to scan_bill_for_errors] Detect CPT unbundling, mutually exclusive code pairs, and NCCI edit violations in a set of codes. Implemented by the bill scanner's anomaly engine.\n\nWHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them.\n\nWHEN NOT: For full bill scans (use scan_bill_for_errors).","read_only":false},{"name":"fair_price_estimator","title":"","description":"[Taxonomy B.8 — delegates to benchmark_payer_rate] Fair-market price distribution for a service: DP-noised percentiles (p10, p25, p50, p75, p90) for the given CPT in a ZIP3 region.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill","read_only":false},{"name":"price_variance_analyzer","title":"","description":"[Taxonomy B.9 — baseline response (public data only)] Given a target price and a CPT+region, return how many standard deviations above/below the market the target sits, plus confidence.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan","read_only":false},{"name":"claim_consistency_checker","title":"","description":"[Taxonomy C.14 — delegates to scan_bill_for_errors] Detect internal contradictions in a claim: time mismatches, mutually exclusive codes, missing required fields, patient-gender/procedure mismatches.\n\nWHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment.\n\nWHEN NOT: For an already-submitted and denied claim, use generate_appeal","read_only":false},{"name":"bundling_violation_detector","title":"","description":"[Taxonomy C.16 — delegates to scan_bill_for_errors] Detect CPT unbundling (billing components of a procedure separately to inflate the claim). Uses the CMS NCCI edits plus payer-specific bundling rules.\n\nWHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment.\n\nWHEN NOT: For an already-submitted and denied claim, use generate_app","read_only":false},{"name":"appeal_success_predictor","title":"","description":"[Taxonomy E.25 — delegates to estimate_appeal_success] Given a denial, predict the probability of a successful appeal. Returns probability with 95% CI, sample size, and recommended appeal-strategy tags.\n\nWHEN TO USE: User or caller wants a probabilistic estimate (denial likelihood, appeal success, payment delay, etc.) to decide whether to pursue a path.\n\nWHEN NOT: For hard facts (dollar amounts, c","read_only":false},{"name":"generate_appeal_letter_v2","title":"","description":"[Taxonomy F.28 — delegates to generate_appeal_letter] [Taxonomy alias] Generate a state-specific insurance appeal letter with UPL-safe disclaimers for 19 US states. Same impl as generate_appeal_letter.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an app","read_only":false},{"name":"negotiation_strategy_generator","title":"","description":"[Taxonomy F.30 — baseline response (public data only)] Given a bill + patient situation, generate a ranked negotiation strategy: hardship appeal, charity-care application, itemization request, phone scripts.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting ","read_only":false},{"name":"insurance_response_interpreter","title":"","description":"[Taxonomy F.31 — baseline response (public data only)] Parse an insurer's response letter or EOB into structured fields: denial reason codes, appeal rights, deadlines, next-step recommendations.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, us","read_only":false},{"name":"settlement_optimizer","title":"","description":"[Taxonomy F.32 — baseline response (public data only)] For a disputed bill, compute the optimal settlement target price balancing probability of acceptance against amount saved.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_exp","read_only":false},{"name":"patient_cost_forecaster","title":"","description":"[Taxonomy H.38 — baseline response (public data only)] Given a patient's plan + predicted care needs, forecast annual out-of-pocket spend across expected claims.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (genera","read_only":false},{"name":"insurance_plan_optimizer","title":"","description":"[Taxonomy H.39 — baseline response (public data only)] Given a patient's historical claim patterns, rank available insurance plans by expected annual cost.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_app","read_only":false},{"name":"cash_vs_insurance_optimizer","title":"","description":"[Taxonomy H.41 — baseline response (public data only)] For a given service + patient plan, determine whether cash-pay + charity-care beats insurance billing.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_a","read_only":false},{"name":"financial_risk_exposure_model","title":"","description":"[Taxonomy H.42 — baseline response (public data only)] Quantify a patient's financial exposure to medical-debt risk given current plan, health status, and historical claim volatility.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or a","read_only":false},{"name":"cpt_to_icd_mapper","title":"","description":"[Taxonomy II.21 — baseline response (public data only)] For a given CPT, surface the ICD-10 codes typically paired with it for medical-necessity support.\n\nWHEN TO USE: User has a CPT code and wants to know what ICD-10 diagnoses commonly pair with it for medical-necessity support.\n\nWHEN NOT: For specific payer policy lookups (code_validation).\n\nEXAMPLES:\n- Common ICDs for 99213: `{\"cpt_code\":\"99213","read_only":false},{"name":"icd_to_cpt_mapper","title":"","description":"[Taxonomy II.22 — baseline response (public data only)] For a given ICD-10, surface the CPT codes typically billed for that diagnosis.\n\nWHEN TO USE: User has an ICD-10 diagnosis and wants to know what CPTs are commonly billed for it.\n\nWHEN NOT: For planning specific services (use benchmark_payer_rate once the CPT is chosen).\n\nEXAMPLES:\n- Common CPTs for essential hypertension: `{\"icd10_code\":\"I10\"","read_only":false},{"name":"code_bundle_validator","title":"","description":"[Taxonomy II.25 — baseline response (public data only)] Check a set of CPT codes against NCCI bundling rules (distinct from modifier-based unbundling).\n\nWHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them.\n\nWHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use gen","read_only":false},{"name":"unbundling_detector","title":"","description":"[Taxonomy II.26 — delegates to scan_bill_for_errors] Detect CPT unbundling patterns in a claim. Alias of scan_bill_for_errors.\n\nWHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them.\n\nWHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use generate_appeal_letter).","read_only":false},{"name":"cash_price_estimator","title":"","description":"[Taxonomy III.39 — baseline response (public data only)] Estimate a fair cash price for a service in a given region (no-insurance path).\n\nWHEN TO USE: Uninsured/self-pay user wants a fair-market cash price for a service. Returns Medicare national as a floor + commercial-multiple band.\n\nWHEN NOT: For insurance-covered scenarios (deductible_impact_calculator + coinsurance_simulator).\n\nEXAMPLES:\n- Ca","read_only":false},{"name":"zip_based_price_variance","title":"","description":"[Taxonomy III.41 — baseline response (public data only)] Report price variance for a CPT across ZIP3 regions with DP noise.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estima","read_only":false},{"name":"regional_price_benchmark","title":"","description":"[Taxonomy III.43 — baseline response (public data only)] Regional price benchmark for a CPT at state/metro/ZIP3 granularity.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estim","read_only":false},{"name":"specialty_price_benchmark","title":"","description":"[Taxonomy III.44 — baseline response (public data only)] Price benchmark for a CPT within a specific provider specialty.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates","read_only":false},{"name":"inflation_adjusted_price_model","title":"","description":"[Taxonomy III.46 — baseline response (public data only)] Inflation-adjusted price comparison across years for a CPT.\n\nWHEN TO USE: User has a historical dollar amount and wants it adjusted for medical-care inflation to a given year.\n\nWHEN NOT: For current market prices (benchmark_payer_rate).\n\nEXAMPLES:\n- Adjust $1K 3yr forward at medical CPI: `{\"base_amount_usd\":1000,\"years\":3}`","read_only":false},{"name":"deductible_impact_calculator","title":"","description":"[Taxonomy III.48 — baseline response (public data only)] Estimate how a planned service will draw against the member's deductible.\n\nWHEN TO USE: User wants to know how a specific charge affects their deductible (how much draws down, remaining after, post-deductible exposure).\n\nWHEN NOT: For total annual out-of-pocket across a year (healthcare_budget_forecaster).\n\nEXAMPLES:\n- Compute deductible dra","read_only":false},{"name":"coinsurance_simulator","title":"","description":"[Taxonomy III.49 — baseline response (public data only)] Simulate member coinsurance exposure across plan-design variants.\n\nWHEN TO USE: User wants to model their coinsurance share of a post-deductible charge. Pass charge_usd and optionally coinsurance_rate.\n\nWHEN NOT: For flat-copay services (copay_model).\n\nEXAMPLES:\n- Simulate 20% coinsurance on $1K: `{\"charge_usd\":1000,\"coinsurance_rate\":0.2}`","read_only":false},{"name":"copay_model","title":"","description":"[Taxonomy III.50 — baseline response (public data only)] Model member copay for a service by plan-design class.\n\nWHEN TO USE: User wants the typical copay for a service type (primary / specialist / er). Uses KFF EHBS 2024 averages.\n\nWHEN NOT: For patient-specific plan details — copay varies by plan design.\n\nEXAMPLES:\n- Typical specialist copay: `{\"service_type\":\"specialist\"}`","read_only":false},{"name":"billing_charge_vs_allowed_delta","title":"","description":"[Taxonomy III.51 — baseline response (public data only)] Delta between billed charge and payer-allowed amount for a claim line.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path es","read_only":false},{"name":"price_anomaly_detector","title":"","description":"[Taxonomy III.52 — baseline response (public data only)] Detect service-line prices statistically anomalous versus market.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimat","read_only":false},{"name":"overpriced_service_detector","title":"","description":"[Taxonomy III.53 — baseline response (public data only)] Flag services billed materially above market percentile thresholds.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estim","read_only":false},{"name":"market_price_distribution_model","title":"","description":"[Taxonomy III.55 — baseline response (public data only)] Full DP-noised market price distribution for a CPT+region pair.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates","read_only":false},{"name":"price_outlier_detector","title":"","description":"[Taxonomy III.56 — baseline response (public data only)] Detect claim-line outliers relative to a learned market distribution.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path est","read_only":false},{"name":"procedure_cost_decomposition","title":"","description":"[Taxonomy III.57 — baseline response (public data only)] Decompose the cost of a procedure into component services + facility + professional fees.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. Fo","read_only":false},{"name":"price_recommendation_engine","title":"","description":"[Taxonomy III.58 — baseline response (public data only)] Recommend a reasonable price to propose to a provider for a service (self-pay or negotiation).\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionabl","read_only":false},{"name":"claim_duplicate_line_detector","title":"","description":"[Taxonomy IV.75 — baseline response (public data only)] Detect duplicated service lines within a single claim.\n\nWHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment.\n\nWHEN NOT: For an already-submitted and denied claim, use generate_appeal_letter. For market pricing context, use benchmark_payer_rate.","read_only":false},{"name":"denial_reason_classifier","title":"","description":"[Taxonomy VI.106 — baseline response (public data only)] Classify a denial letter or remittance advice into normalized denial-reason categories.\n\nWHEN TO USE: User or caller wants a probabilistic estimate (denial likelihood, appeal success, payment delay, etc.) to decide whether to pursue a path.\n\nWHEN NOT: For hard facts (dollar amounts, code definitions, deadlines). Predictions carry confidence ","read_only":false},{"name":"appeal_argument_generator","title":"","description":"[Taxonomy VII.120 — baseline response (public data only)] Generate component arguments for an appeal letter: medical-necessity, contract, policy.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a nego","read_only":false},{"name":"denial_response_builder","title":"","description":"[Taxonomy VII.121 — baseline response (public data only)] Build a denial-response package tailored to the denial reason code.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a no","read_only":false},{"name":"dispute_case_builder","title":"","description":"[Taxonomy VII.123 — baseline response (public data only)] Assemble a complete dispute case file including claim, denial, evidence, and timeline.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negot","read_only":false},{"name":"evidence_pack_generator","title":"","description":"[Taxonomy VII.124 — baseline response (public data only)] Generate an evidence package supporting a claim or appeal (references, studies, policies).\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a n","read_only":false},{"name":"claim_rebuttal_generator","title":"","description":"[Taxonomy VII.128 — baseline response (public data only)] Generate a rebuttal to a payer's denial rationale point-by-point.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-","read_only":false},{"name":"appeal_escalation_path_finder","title":"","description":"[Taxonomy VII.129 — baseline response (public data only)] Find the correct escalation path for a denied claim (internal appeal → external review → DOI).\n\nWHEN TO USE: User needs to know the deadlines and agencies for each step of appealing a denial. Pass state (e.g. 'CA') and insurer for state-specific and insurer-specific values.\n\nWHEN NOT: Without state/insurer — still works but returns generic ","read_only":false},{"name":"payer_specific_appeal_templates","title":"","description":"[Taxonomy VII.130 — baseline response (public data only)] Return payer-specific appeal templates known to perform well.\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-deni","read_only":false},{"name":"denial_code_explainer","title":"","description":"[Taxonomy VII.131 — baseline response (public data only)] Explain a CARC/RARC denial code in plain language with common causes.\n\nWHEN TO USE: User asks 'what does CO-16 mean' or similar — any CARC/RARC code. Returns full X12 table entry when available with meaning, category, typical root cause, primary remediation, and reversibility flag.\n\nWHEN NOT: For drafting an appeal (generate_appeal_letter).","read_only":false},{"name":"claim_reconsideration_builder","title":"","description":"[Taxonomy VII.132 — baseline response (public data only)] Build a claim reconsideration request (lighter-weight than a formal appeal).\n\nWHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one.\n\nWHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation pat","read_only":false},{"name":"supporting_document_selector","title":"","description":"[Taxonomy VII.135 — baseline response (public data only)] Select optimal supporting documents for an appeal from an available document pool.\n\nWHEN TO USE: User is preparing an appeal and needs a ranked list of supporting documents for the denial category. Pass denial_code.\n\nWHEN NOT: Without denial_code — still returns generic docs but category-specific ranking is the high-value output.\n\nEXAMPLES:","read_only":false},{"name":"out_of_pocket_optimizer","title":"","description":"[Taxonomy X.174 — baseline response (public data only)] Optimize out-of-pocket spend across a sequence of planned services.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false},{"name":"financial_exposure_model","title":"","description":"[Taxonomy X.176 — delegates to financial_risk_exposure_model] Model a member's financial exposure. Alias of financial_risk_exposure_model.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false},{"name":"procedure_affordability_ranker","title":"","description":"[Taxonomy X.177 — baseline response (public data only)] Rank a set of procedures by affordability for a given member.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false},{"name":"treatment_cost_comparator","title":"","description":"[Taxonomy X.178 — baseline response (public data only)] Compare expected costs across treatment alternatives for a condition.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false},{"name":"bill_shock_predictor","title":"","description":"[Taxonomy X.179 — baseline response (public data only)] Predict risk that a planned service will trigger an unexpected large bill.\n\nWHEN TO USE: User planning a service and wants to know if it will trigger an unexpected-large-bill situation. Pass expected_charge_usd and optionally cpt_code to get Medicare-ratio context.\n\nWHEN NOT: For a bill already received — scan_bill_for_errors first.\n\nEXAMPLES","read_only":false},{"name":"payment_plan_optimizer","title":"","description":"[Taxonomy X.180 — baseline response (public data only)] Optimize a payment plan structure for a patient balance.\n\nWHEN TO USE: User has a balance and wants to structure a payment plan. Pass balance_usd and months.\n\nWHEN NOT: If user may qualify for charity care — run financial_assistance_finder first.\n\nEXAMPLES:\n- 12-month plan for $3K balance: `{\"balance_usd\":3000,\"months\":12}`","read_only":false},{"name":"financial_assistance_finder","title":"","description":"[Taxonomy X.181 — baseline response (public data only)] Find applicable financial-assistance programs (hospital charity, 340B, state, pharma).\n\nWHEN TO USE: User needs help paying a medical bill. Pass household_income_usd and family_size for FPL-based eligibility flags across 6 programs (501(r) charity, Medicaid, PE, manufacturer PAPs, 340B, state pools).\n\nWHEN NOT: For insured users with low expo","read_only":false},{"name":"patient_cost_explainer","title":"","description":"[Taxonomy X.182 — baseline response (public data only)] Explain why a specific charge appears on a bill in plain language.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false},{"name":"healthcare_budget_forecaster","title":"","description":"[Taxonomy X.183 — baseline response (public data only)] Forecast a household's annual healthcare spend based on plan + utilization.\n\nWHEN TO USE: User planning annual healthcare spend, comparing plans, or estimating worst-case exposure.\n\nWHEN NOT: For a specific procedure cost (benchmark_payer_rate).\n\nEXAMPLES:\n- Forecast annual spend range: `{}`","read_only":false},{"name":"medical_spending_analyzer","title":"","description":"[Taxonomy X.184 — baseline response (public data only)] Analyze a patient's medical spending over a period and surface optimization opportunities.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_lette","read_only":false},{"name":"insurance_value_optimizer","title":"","description":"[Taxonomy X.185 — baseline response (public data only)] Recommend insurance-plan selections to maximize value given projected utilization.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false},{"name":"patient_financial_risk_score","title":"","description":"[Taxonomy X.186 — baseline response (public data only)] Score a patient's financial risk exposure from planned or ongoing care.\n\nWHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan.\n\nWHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).","read_only":false}],"server_info":{"name":"medigami-public","version":"1.28.1"},"category":"health","tags":["finance","agents","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-07","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-medigami-mcp/"}