FineRx MCP server
Related Servers
Alternatives to FineRx MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search for real-time prescription drug prices, find local pharmacies, and retrieve discount coupons through the GoodRx service. It uses Playwright browser automation to provide drug comparisons and checkout details like BIN and PCN codes.513 npmMIT
- AlicenseNot gradedqualityCmaintenanceUnifies five public US-government drug datasets into a single sourced page per GLP-1/cardiometabolic drug, providing cost, shortage, label, and alternatives. The MCP server exposes the same Drug contract as the UI for agent-native access.71,212,500 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up dated, source-linked US GLP-1 medication prices — cheapest month-to-month programs, per-provider price history and changes, manufacturer cash-pay ladders, and a monthly price index — filterable by drug, provider, form and billing. It is read-only and needs no account or API key.MIT
- AlicenseNot gradedqualityBmaintenanceEnables comparing US prescription prices across pharmacy chains, finding nearby pharmacies, and identifying foreign drug equivalents through forwarded FineRx tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative sources like FDA, WHO, PubMed, RxNorm, and Google Scholar for drug information, health statistics, clinical guidelines, trials, and medical literature. It runs locally with no API keys, so data stays private while results come back with evidence grading and resilient fallbacks.83 npmISC
- FlicenseBqualityDmaintenanceEnables AI agents to query free biomedical and pharmaceutical APIs for clinical trials, drug data, molecular structures, adverse events, and research literature.14-
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: search/get/compare for drugs, find_us_equivalent vs foreign_brands_for_drug are cleanly separated by direction, and get_savings_card vs email_savings_card are distinct (retrieve vs send). The only mild overlap is get_drug vs compare_prices (both return prices), but their inputs and outputs differ enough (slug vs NDC) that an agent can choose correctly.
The set mostly follows a verb_noun pattern: search_drugs, get_drug, compare_prices, find_nearby_pharmacies, get_dataset_info, get_savings_card, email_savings_card, get_prescription_options, find_us_equivalent, foreign_brands_for_drug. Minor deviations: find_us_equivalent and foreign_brands_for_drug use a different verb style (find/foreign_brands_for) than the get_/search_/compare_/email_ pattern, but they are still readable and predictable.
10 tools is well within the ideal 3-15 range and each tool covers a distinct aspect of the domain: search, details, price comparison, pharmacy locations, dataset info, savings card, email, prescription options, and international equivalence (both directions). No tool feels redundant or extraneous.
The domain is consumer prescription savings, and the surface covers the full journey: resolving a drug name (search_drugs), getting details (get_drug), comparing prices (compare_prices), finding pharmacies (find_nearby_pharmacies), getting/sending the savings card (get_savings_card, email_savings_card), handling no-prescription or brand-costly situations (get_prescription_options), and international drug mapping in both directions (find_us_equivalent, foreign_brands_for_drug). Dataset info and attribution are also covered. No obvious dead ends.