Skip to main content
Glama
rirko

shdc-appointment-mcp

by rirko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to shdc-appointment-mcp

No user-submitted related servers found.

    Related Servers

    • wxauto-mcp-sse

      bjdr69
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WeChat automation, supporting message sending, chat history retrieval, and contact list management via SSE protocol.
      5
      -

    • mcp-cirujanos

      zobra-auto
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for scheduling appointments and managing services for plastic surgery clinics. Supports calendar operations, booking, catalog search, and case studies (before/after) for procedures.
      -

    • MCP Appointment Booking Server

      Manish-Awase
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables users to book, cancel, reschedule, and list appointments through natural language interactions. It uses YAML configurations for agent behavior and function logic to manage appointment data and availability.
      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

    B3/5.0

    Scored across 40 tools

    Disambiguation5/5

    Each tool belongs to a clear domain (appointment, auth, health, etc.) with distinct actions. Even within health, tools like health_document_get vs health_document_export have clear differences documented. No two tools have overlapping purposes.

    Naming Consistency4/5

    Tools follow a consistent snake_case pattern with domain prefixes. Most use verb-last convention (e.g., health_allergy_list), but a few like list_patients use verb-first. This minor inconsistency does not impair readability.

    Tool Count2/5

    With 40 tools, the server is over-scoped. While each tool has a distinct purpose, the sheer number makes it cumbersome for an agent. Splitting into separate servers (e.g., appointments, health records) would improve coherence.

    Completeness4/5

    The tool surface covers authentication, registration, appointment booking, health records, and drug interactions. Missing update/delete for several health entities (e.g., allergy, document, timeline) are minor gaps that agents can work around.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources