Medigami MCP

ติดตั้ง

เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง

ผลตรวจผ่าน 2/3 · สิ่งที่คุณถามผ่านเซิร์ฟเวอร์ของผู้ทำ (mcp.medigami.com)

claude mcp add --transport http --scope user medigami https://mcp.medigami.com/public/mcp

{
  "mcpServers": {
    "medigami": {
      "url": "https://mcp.medigami.com/public/mcp"
    }
  }
}

{
  "servers": {
    "medigami": {
      "type": "http",
      "url": "https://mcp.medigami.com/public/mcp"
    }
  }
}

ใช้กับโปรแกรมไหนได้

ดูจากแบบการต่อของ server ตัวนี้ และเอกสารของผู้ทำโปรแกรมแต่ละตัว ตรวจเมื่อ 10 พ.ย. 2569

ต่อผ่านคลาวด์ได้ใน

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

ดูโปรแกรมทั้งหมดพร้อมข้อดีข้อเสีย →

ทำอะไรได้บ้าง

ชื่อและคำอธิบายเครื่องมือตามที่ server ตอบมาเมื่อ 9 พ.ย. 2569 ผู้ทำเป็นคนเขียน ไม่ใช่เรา แสดงเป็นข้อความล้วน

• scan_bill_for_errors

  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. PHI WARNING: bill text typically contains PHI (patient name, DOB, MRN, insurer

• generate_appeal_letter

  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. WHEN TO US

• optimize_prescription

  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. WHEN TO USE: User asks about prescription cost — lowest-pr

• analyze_glp1_pathways

  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. WHEN TO USE: User

• verify_attestation

  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, reaso

• watch_appeal_outcome

  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 estim

• watch_claim_denial

  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. WHEN TO USE: Caller wants to

• format_citation

  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 c

• submit_denial_letter

  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 fie

• verify_mcp_response

  DEPRECATED ALIAS of verify_attestation — kept for backward compatibility with v0.1.7 clients. New code should call verify_attestation directly. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signa

• format_medigami_citation

  DEPRECATED ALIAS of format_citation — kept for backward compatibility with v0.1.7 clients. New code should call format_citation directly. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature,

• estimate_appeal_success

  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 l

• resolve_denial

  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

• maximize_recovery

  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. WHEN TO USE: User has already run scan_bill_for_errors and wants the anomalies ranked by

• explain_appeal_success

  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 alongsi

• negotiate_bill_script

  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

• batch_scan_bills

  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. WHEN TO USE:

• lookup_icd10

  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 u

• lookup_cpt

  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; ful

• lookup_npi

  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 AP

• verify_dea_authorization

  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 we

• lookup_provider_taxonomy

  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). WHEN TO USE: Resol

• resolve_codes

  [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 run

• code_conflict_detector

  [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. WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whet

• fair_price_estimator

  [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. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions

• price_variance_analyzer

  [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. WHEN TO USE: User wants to understand what a service typically costs, compare prices across re

• claim_consistency_checker

  [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. WHEN TO USE: Caller is building or validating a claim payload before submission

• bundling_violation_detector

  [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. WHEN TO USE: Caller is building or validating a claim payload before submissi

• appeal_success_predictor

  [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. WHEN TO USE: User or caller wants a probabilistic estimate (denial likelihood

• generate_appeal_letter_v2

  [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. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing argu

• negotiation_strategy_generator

  [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. WHEN TO USE: User has a denied claim and wants to appeal, or is preparin

• insurance_response_interpreter

  [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. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments /

• settlement_optimizer

  [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. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escal

• patient_cost_forecaster

  [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. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or tryi

• insurance_plan_optimizer

  [Taxonomy H.39 — baseline response (public data only)] Given a patient's historical claim patterns, rank available insurance plans by expected annual cost. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to

• cash_vs_insurance_optimizer

  [Taxonomy H.41 — baseline response (public data only)] For a given service + patient plan, determine whether cash-pay + charity-care beats insurance billing. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying t

• financial_risk_exposure_model

  [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. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financi

• cpt_to_icd_mapper

  [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. WHEN TO USE: User has a CPT code and wants to know what ICD-10 diagnoses commonly pair with it for medical-necessity support.

• icd_to_cpt_mapper

  [Taxonomy II.22 — baseline response (public data only)] For a given ICD-10, surface the CPT codes typically billed for that diagnosis. WHEN TO USE: User has an ICD-10 diagnosis and wants to know what CPTs are commonly billed for it. WHEN NOT: For planning specific services (use b

• code_bundle_validator

  [Taxonomy II.25 — baseline response (public data only)] Check a set of CPT codes against NCCI bundling rules (distinct from modifier-based unbundling). WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map

• unbundling_detector

  [Taxonomy II.26 — delegates to scan_bill_for_errors] Detect CPT unbundling patterns in a claim. Alias of scan_bill_for_errors. WHEN 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. WHEN NOT: F

• cash_price_estimator

  [Taxonomy III.39 — baseline response (public data only)] Estimate a fair cash price for a service in a given region (no-insurance path). WHEN TO USE: Uninsured/self-pay user wants a fair-market cash price for a service. Returns Medicare national as a floor + commercial-multiple b

• zip_based_price_variance

  [Taxonomy III.41 — baseline response (public data only)] Report price variance for a CPT across ZIP3 regions with DP noise. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonabl

• regional_price_benchmark

  [Taxonomy III.43 — baseline response (public data only)] Regional price benchmark for a CPT at state/metro/ZIP3 granularity. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonab

• specialty_price_benchmark

  [Taxonomy III.44 — baseline response (public data only)] Price benchmark for a CPT within a specific provider specialty. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.

• inflation_adjusted_price_model

  [Taxonomy III.46 — baseline response (public data only)] Inflation-adjusted price comparison across years for a CPT. WHEN TO USE: User has a historical dollar amount and wants it adjusted for medical-care inflation to a given year. WHEN NOT: For current market prices (benchmark_p

• deductible_impact_calculator

  [Taxonomy III.48 — baseline response (public data only)] Estimate how a planned service will draw against the member's deductible. WHEN TO USE: User wants to know how a specific charge affects their deductible (how much draws down, remaining after, post-deductible exposure). WHEN

• coinsurance_simulator

  [Taxonomy III.49 — baseline response (public data only)] Simulate member coinsurance exposure across plan-design variants. WHEN TO USE: User wants to model their coinsurance share of a post-deductible charge. Pass charge_usd and optionally coinsurance_rate. WHEN NOT: For flat-cop

• copay_model

  [Taxonomy III.50 — baseline response (public data only)] Model member copay for a service by plan-design class. WHEN TO USE: User wants the typical copay for a service type (primary / specialist / er). Uses KFF EHBS 2024 averages. WHEN NOT: For patient-specific plan details — cop

• billing_charge_vs_allowed_delta

  [Taxonomy III.51 — baseline response (public data only)] Delta between billed charge and payer-allowed amount for a claim line. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reaso

• price_anomaly_detector

  [Taxonomy III.52 — baseline response (public data only)] Detect service-line prices statistically anomalous versus market. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable

• overpriced_service_detector

  [Taxonomy III.53 — baseline response (public data only)] Flag services billed materially above market percentile thresholds. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonab

• market_price_distribution_model

  [Taxonomy III.55 — baseline response (public data only)] Full DP-noised market price distribution for a CPT+region pair. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.

• price_outlier_detector

  [Taxonomy III.56 — baseline response (public data only)] Detect claim-line outliers relative to a learned market distribution. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reason

• procedure_cost_decomposition

  [Taxonomy III.57 — baseline response (public data only)] Decompose the cost of a procedure into component services + facility + professional fees. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a bil

• price_recommendation_engine

  [Taxonomy III.58 — baseline response (public data only)] Recommend a reasonable price to propose to a provider for a service (self-pay or negotiation). WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether

• claim_duplicate_line_detector

  [Taxonomy IV.75 — baseline response (public data only)] Detect duplicated service lines within a single claim. WHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment. WHEN NOT: For an already-submitted and deni

• denial_reason_classifier

  [Taxonomy VI.106 — baseline response (public data only)] Classify a denial letter or remittance advice into normalized denial-reason categories. WHEN TO USE: User or caller wants a probabilistic estimate (denial likelihood, appeal success, payment delay, etc.) to decide whether t

• appeal_argument_generator

  [Taxonomy VII.120 — baseline response (public data only)] Generate component arguments for an appeal letter: medical-necessity, contract, policy. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: F

• denial_response_builder

  [Taxonomy VII.121 — baseline response (public data only)] Build a denial-response package tailored to the denial reason code. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a

ผลตรวจเบื้องต้นi

เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 12 พ.ย. 2569

• ! ควรระวัง

  ตัวตนผู้ทำตรงกับ repo

  ทะเบียนไม่ได้ระบุ repo ของโค้ด จึงยังจับคู่ผู้ลงทะเบียน (medigami.com) กับโค้ดไม่ได้

• … ยังไม่ตรวจ

  ยังมีคนดูแล

  ยังไม่ได้อ่านข้อมูล repo จาก GitHub

• … ยังไม่ตรวจ

  มีสัญญาอนุญาต (license)

  ยังไม่ได้อ่านข้อมูล repo จาก GitHub

• ✓ ผ่าน

  endpoint ตอบ

  ตอบกลับใน 216 ms (HTTP 200)

• – ไม่เกี่ยว

  ล็อกอินแบบ OAuth

  ไม่ต้องล็อกอิน

• ✓ ผ่าน

  คำอธิบายเครื่องมือไม่มีคำสั่งแอบแฝง

  อ่านคำอธิบายเครื่องมือ 60 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI

รีวิวจากผู้ใช้

ยังไม่มีรีวิว

เข้าสู่ระบบด้วย Google เพื่อเขียนรีวิว

เทียบกับตัวอื่นในหมวด คลินิกและสุขภาพi

• ดาวมากกว่า 0% ของอีก 1089 ตัวในหมวดนี้
• ส่งรุ่นใหม่เข้า registry ล่าสุดกว่า 33% ของอีก 1089 ตัวในหมวดนี้
• ผลตรวจเบื้องต้นดีกว่าหรือเท่ากับ 51% ของอีก 1089 ตัวในหมวดนี้

เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo

ตัวอื่นในหมวดเดียวกัน

server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว

อ่านการ์ด:↓ ดาวน์โหลดต่อสัปดาห์i★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi

Medplum MCP

Securely access and manage FHIR healthcare data stored in Medplum.

โดย medplum·ใช้กันมาก·★ 2.8K·อัปเดต 4 เดือนที่ผ่านมา

รันบนคลาวด์✓ เจ้าของบริการ · medplum.com

ติดตั้ง

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

โดย thetahealth·กำลังโต·↓ 290/สัปดาห์·★ 1.5K·อัปเดต เมื่อวานซืน

รันบนเครื่อง✓ thetahealth.ai

ติดตั้ง

Apple Health

Local-first Apple Health MCP server for questions about your sleep, workouts and heart data.

โดย neiltron·กำลังโต·↓ 106/สัปดาห์·★ 575·อัปเดต 2 เดือนที่ผ่านมา

รันบนเครื่อง

ติดตั้ง

README จากผู้ทำ

ไม่พบ README ใน repo