iran-doctor-mcp
Related Servers
Alternatives to iran-doctor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to search a directory of Iranian doctors by full or partial name, city or province, and specialty, and returns the best match with alternatives plus clinic addresses, phones, weekly hours, and map links. It is read-only and requires no authentication, so it cannot book appointments or provide medical advice.354 PyPI1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search Iranian doctors, hospitals and clinics by specialty, city, name, gender and online visit, then read profiles, ratings, insurances, patient reviews, visit prices in Toman and free appointment times. Read-only, with no login, booking or payment, so users compare options and get a profile link to book themselves.12375 PyPI4PolyForm Noncommercial 1.0.0
- AlicenseAqualityBmaintenanceEnables AI agents to search Iranian doctors by speciality, city, neighborhood, insurance and visit type, compare office and online consultation fees, check free appointment times up to a month ahead, and read reviews. Also covers hospitals, clinics, labs, pharmacies, fixed-price clinic offers and health articles, all read-only so booking happens on the site via a returned link.14372 PyPI2PolyForm Noncommercial 1.0.0
- FlicenseNot gradedqualityBmaintenanceEnables finding doctors in Romania by county, speciality, language, name, and weekly availability, with fuzzy name matching and nearby-county fallback.-
- AlicenseBqualityCmaintenanceEnables querying Doctolib's public data to find practitioners, retrieve all available appointment slots in a geographic area, access practice details, and receive alerts when new slots open.21MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search and browse an Iranian online pharmacy's catalog read-only, covering prices per variant, ingredients, dosage, warnings, user questions and reviews, product comparisons and alternatives, plus health magazine articles. No API key or account is required.1293 PyPI2PolyForm Noncommercial 1.0.0
TDQS
Scored across 3 tools
The three tools occupy clearly separate roles: aggregate name search across platforms, deep-dive on a single doctor on a single platform, and static platform metadata. The descriptions explicitly state the boundary (search returns summaries/links; details requires one platform + id), so misselection is unlikely.
All three follow a consistent verb_noun snake_case pattern: search_doctor, get_doctor_details, list_platforms. Verb choice (search/get/list) also maps cleanly to the operation type.
Three tools is minimal but each earns its place for a search-aggregator domain, and the surface is not padded. It sits at the low end of the comfortable range, so an extra capability tool (e.g. search by specialty or city browse) would round it out.
Search→details→platform-info covers the discovery lifecycle, and booking links are returned, but search is name-only: there is no browse by specialty, city, or price filter, which are core user intents in doctor discovery. No booking/availability-query operation either, so the workflow dead-ends at an external link.