GPH Intelligence MCP Server — Healthcare Service Provider Finder. Access 100,000
GPH Intelligence MCP Server — Healthcare Service Provider Finder. Access 100,000+ verified providers via MCP.
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://gph-mcp-server.pages.dev/mcp |
|---|---|
| Source | https://github.com/Crindo2/gph-mcp-server |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-06-15 18:17:33 |
| Last checked | 2026-11-17 21:48:05 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 296 / 533 ms |
| Last successful check | 2026-11-17 21:48:05 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
match_practice— Recommend and rank the best healthcare vendors for a specific medical practice. Use this when a practice manager, physician, or administratosearch_providers— Browse and filter the healthcare vendor directory. Use this for open-ended exploration, e.g. "show me medical billing companies in Texas", "get_provider_detail— Get the full profile of one healthcare vendor by slug. Use this after match_practice or search_providers when the user asks to "tell me morelist_categories— List every service category in the GPH vendor directory with its live provider count. Call this FIRST when you do not already know which catget_ehr_product_detail— Read the free versioned EHR product JSON projection by exact product key. Returns the complete HTTP JSON body, including explicit edition repractice_data_counts— Counts practices with headline (strongest-tier) evidence only, by US state and practice segment, from the public Practice Data aggregate end
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:48:05 | ✓ | ✓ | 347 ms | 90 | active |
| 2026-11-17 21:33:00 | ✓ | ✓ | 400 ms | 91 | active |
| 2026-11-17 21:17:49 | ✓ | ✓ | 335 ms | 91 | active |
| 2026-11-17 21:02:46 | ✓ | ✓ | 231 ms | 94 | active |
| 2026-11-17 20:47:25 | ✓ | ✓ | 350 ms | 90 | active |
| 2026-11-17 20:32:21 | ✓ | ✓ | 422 ms | 91 | active |
| 2026-11-17 20:17:14 | ✓ | ✓ | 498 ms | 91 | active |
| 2026-11-17 20:01:37 | ✓ | ✓ | 374 ms | 91 | active |
| 2026-11-17 19:46:21 | ✓ | ✓ | 380 ms | 91 | active |
| 2026-11-17 19:31:16 | ✓ | ✓ | 346 ms | 91 | active |
| 2026-11-17 19:16:10 | ✓ | ✓ | 393 ms | 91 | active |
| 2026-11-17 19:00:32 | ✓ | ✓ | 245 ms | 94 | active |
| 2026-11-17 18:45:30 | ✓ | ✓ | 270 ms | 94 | active |
| 2026-11-17 18:30:29 | ✓ | ✓ | 370 ms | 91 | active |
| 2026-11-17 18:15:26 | ✓ | ✓ | 442 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://gph-mcp-server.pages.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/gph-mcp-server-pages-dev-mcp # JSON