Skip to main content
Glama
JondaHealthTech

JondaX MCP Server

Official
by JondaHealthTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to JondaX MCP Server

No user-submitted related servers found.

    Related Servers

    • carechronicle-mcp

      Ankithraj-1312
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to interact with clinical patient records using tools for document ingestion, structured conversion, patient profiling, record listing, search, and secure Q&A over patient documentation.
      -

    • ParseFlow MCP Server

      Libres-coder
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to parse and search documents including PDF, Word, Excel, PowerPoint, and images via OCR, with support for semantic search and batch processing.
      2
      MIT

    • Healthcare Document

      hpaamu
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables document search, grounded question answering, summarization, patient timeline extraction, and PHI redaction for healthcare documents using retrieval-augmented generation.
      -

    • DICOM MCP Server

      Y5ive9ine
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query, read, download, and move medical imaging data on DICOM servers (PACS, VNA) including patient searches, study retrieval, PDF report extraction, and image transfer to AI endpoints for analysis.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The two upload tools are distinguished by document type (pathology/blood test vs medical device), and the two retrieval tools are clearly separated by status vs results. There is minor potential confusion because both upload tools trigger the same OCR/extraction pipeline, but descriptions are clear enough.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: upload_* for ingestion and get_* for retrieval. The naming is predictable and easy to navigate.

    Tool Count5/5

    Four tools is well-scoped for the server's purpose: upload two categories of medical documents, check status, and retrieve results. Each tool earns its place with no unnecessary redundancy.

    Completeness4/5

    The core workflow of upload → status → results is fully covered. Minor gaps exist around error details or listing past uploads, but agents can successfully complete the primary extraction workflow without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources