Skip to main content
Glama
Sign In
Medical Calculator MCP Server

Medical Calculator MCP Server

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Medical Calculator MCP Server

No user-submitted related servers found.

    Related Servers

    • FHIR MCP Server

      Sharma8610
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to query and manipulate clinical data on a FHIR-compliant backend through CRUD resource tools, document ingestion, semantic search, and terminology lookup.
      -

    • CharmHealth MCP Server

      Talha-2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and MCP clients to interact with patient records, encounters, and practice information through tools for clinical, scheduling, messaging, and administrative workflows.
      MIT

    • MedCalc MCP Server

      vitaldb
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides 59 clinical medical calculators and scoring tools for healthcare professionals and AI assistants, covering renal, cardiovascular, pulmonary, critical care, and other specialties.
      5
      MIT

    • CharmHealth MCP Server

      talharazzaq-sudo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and MCP clients to interact with patient records, encounters, and practice information through an EHR API. It provides 16 tools for clinical, administrative, and communication workflows including appointments, medications, labs, tasks, messaging, and fax.
      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.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    The three discovery tools (discover, find_tools_by_params, get_related_tools) have distinct primary intents—categorical discovery, reverse parameter lookup, and similarity-based relatedness—but they could still be confused in edge cases, especially discover(by='keyword') versus find_tools_by_params. The calculation tools are clearly distinct.

    Naming Consistency4/5

    All names use snake_case and imperative verbs, which is consistent, but the pattern is not uniformly verb_noun: 'discover' and 'calculate' are bare verbs while others have objects. This is a minor deviation rather than a chaotic mix.

    Tool Count5/5

    Six tools is well-scoped for a meta-server wrapping 75+ calculator implementations. The surface is kept small by exposing discovery, schema retrieval, single calculation, and batch calculation rather than one tool per calculator.

    Completeness5/5

    The server covers the full workflow: discover available tools, inspect required schemas, run single or batch calculations, and find alternative/related calculators. Since calculators are static and read-only, no update/delete operations are expected. The tool set leaves no obvious dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources