Public MCP server comparing U.S. telehealth programs (GLP-1, TRT, longevity): pr
Public MCP server comparing U.S. telehealth programs (GLP-1, TRT, longevity): prices, fees, labs, LegitScript — every value sourced
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://telehealthnearme.pro/mcp |
|---|---|
| Source | https://github.com/X1native-code/telehealthnearme-mcp |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-11-10 20:53:35 |
| Last checked | 2026-11-17 22:03:38 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 286 / 525 ms |
| Last successful check | 2026-11-17 22:03:38 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
list_categories— Lists the U.S. telehealth specialties this server covers, with each specialty’s slug, the treatment keys it accepts (for example semaglutidefind_programs— Finds online telehealth programs in one U.S. specialty and sorts them by lowest advertised monthly price. Use it when the user asks which onget_program— Returns the full sourced record for one program: every price and plan term, membership and lab fees, approval type, LegitScript status, cavecompare_programs— Compares 2 to 5 programs from the same specialty side by side: monthly prices, membership, approval type, blood work, LegitScript status, excalculate_true_cost— Projects the all-in cost of ONE program + treatment over a chosen number of months, using only that program’s published prices: the intro/fisearch— Finds the most relevant U.S. telehealth programs for a free-text question when you do not know the exact category slug or treatment key. Pas
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:03:38 | ✓ | ✓ | 418 ms | 91 | active |
| 2026-11-17 21:48:37 | ✓ | ✓ | 353 ms | 91 | active |
| 2026-11-17 21:33:37 | ✓ | ✓ | 334 ms | 91 | active |
| 2026-11-17 21:18:36 | ✓ | ✓ | 203 ms | 94 | active |
| 2026-11-17 21:03:35 | ✓ | ✓ | 164 ms | 94 | active |
| 2026-11-17 20:48:34 | ✓ | ✓ | 202 ms | 94 | active |
| 2026-11-17 20:33:33 | ✓ | ✓ | 677 ms | 91 | active |
| 2026-11-17 20:18:32 | ✓ | ✓ | 438 ms | 91 | active |
| 2026-11-17 20:03:31 | ✓ | ✓ | 319 ms | 91 | active |
| 2026-11-17 19:48:30 | ✓ | ✓ | 342 ms | 91 | active |
| 2026-11-17 19:33:29 | ✓ | ✓ | 645 ms | 91 | active |
| 2026-11-17 19:18:28 | ✓ | ✓ | 252 ms | 94 | active |
| 2026-11-17 19:03:21 | ✓ | ✓ | 430 ms | 91 | active |
| 2026-11-17 18:48:11 | ✓ | ✓ | 119 ms | 94 | active |
| 2026-11-17 18:33:10 | ✓ | ✓ | 349 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://telehealthnearme.pro/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/telehealthnearme-pro-mcp # JSON