Skip to main content
Glama
mymedi-ai-mcp-server

mymedi-ai-mcp-server

by MyMedi-AI

Related Servers

Alternatives to mymedi-ai-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to look up ICD-10-CM and HCPCS codes, explain insurance and billing terms, verify EOB arithmetic, and access guides for reading medical bills and explanations of benefits.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      702 pay-per-call tools for AI agents over MCP: documents to text and invoice fields as JSON (PDF, Word, Excel, scans by OCR), web search and page text, company and VAT checks, sanctions screening, blockchain reads and token prices, weather and utilities. Free calls to start.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 89 hosted, pay-per-call tools that let agents capture screenshots, scrape and search the web, convert and extract PDFs and documents, run OCR, handle text-to-speech and speech-to-text, process images, and parse invoices, contracts and compliance checks. Billing is flat per call and charged only on success, with cost and remaining balance returned in each response.
      MIT

    TDQS

    A3.5/5.0

    Scored across 32 tools

    Disambiguation3/5

    Descriptions are unusually explicit about what each tool does not do, which rescues many near-neighbors, but real overlaps remain: reimbursement_basic vs code_reimbursement vs fee_schedule_lookup (and code_lookup's embedded DMEPOS rates) all answer 'what does Medicare pay,' and code_lookup vs code_lookup_basic vs code_lookup_batch differ mainly by price and payload size. The PA family (pa_required_check, pa_predict, pa_status, pa_exposure_report, plus PA checks inside order_readiness_checklist and compliance_audit) is distinguishable only after careful reading. An agent can get there, but misselection is plausible.

    Naming Consistency4/5

    Overwhelmingly snake_case with a domain-ish prefix (code_*, drug_*, pa_*, provider_*), which is readable and mostly predictable. Deviations are ordering inconsistencies — reimbursement_basic vs code_reimbursement, fee_schedule_lookup vs code_lookup, denial_code_info — and a 'basic' suffix convention applied unevenly. Still far more consistent than not.

    Tool Count2/5

    32 tools is well past the 25+ threshold where a surface starts to feel heavy, and the count is inflated by tiered duplicates (basic/full/batch variants of lookup, validate and reimbursement) rather than genuinely distinct operations. A broad domain justifies many tools, but several here earn their place only as billing tiers, not as new capabilities.

    Completeness4/5

    Coverage of the medical coding lifecycle is strong: lookup, suggest, validate, crossref, batch variants, reimbursement/fee schedules, PA checks, claims pre-submission validation, compliance audit and NER extraction, plus adjacent drug, provider, trial and surveillance data. Gaps are acknowledged rather than hidden (no NCCI PTP/MUE edits, no payer-specific policy, drug interactions only statistical), so agents hit few dead ends for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data