Skip to main content
Glama
mcp-availability-server

mcp-availability-server

by JulianThorpe

Related Servers

Alternatives to mcp-availability-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Exposes availability and appointment-proposal tools over stdio so an MCP client can query open slots and suggest bookings, without being able to create them—actual booking requires human confirmation through the separate UI/API. Slot claims are transactional and idempotent, and cancellation only releases a slot still owned by that booking.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to check clinic hours, list open slots, find the next available slot, and create idempotent appointment bookings at HeyDenta clinics through natural language tool calls. Runs over stdio or Streamable HTTP with built-in auth, retries, and a duplicate-booking guard.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only, deterministic tools for searching accounts and knowledge and retrieving tickets, ticket details, and product information over a stdio MCP connection.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides MCP tools to list valid appointment slots, schedule, reschedule, and cancel appointments under a clinic's business policy (hours, buffers, minimum notice, practitioner availability).
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables access to patient records, symptom triage, appointment scheduling, and hospital data lookup through a JSON-RPC MCP interface with HTTP and stdio transports.
      -

    TDQS

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve entirely different purposes—one for checking appointment availability and one for formatting call summaries—so there is no ambiguity between them.

    Naming Consistency5/5

    Both tools use a clear verb_noun pattern with underscores (check_availability and format_call_summary), maintaining consistency.

    Tool Count2/5

    With only two tools covering disparate domains (availability and call summaries), the tool count is too low for coherent scope; each domain would benefit from additional related tools.

    Completeness2/5

    The tool surface is severely incomplete for both implied domains: for availability, CRUD operations are missing; for call summaries, creation and editing are absent, leaving significant gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues