GTH Intelligence — Substance Abuse Treatment Finder
https://server.smithery.ai/cbeggroup/gettreatmenthelp/mcpSearch 12,373 SAMHSA-verified substance abuse treatment facilities across all 50 states by zip code, service type, and competitive density. The GTH Intelligence MCP server gives AI agents real-time access to substance abuse treatment facility data sourced from SAMHSA (Substance Abuse and Mental Health Services Administration). Built for treatment operators, healthcare AI developers, and anyone building tools in the behavioral health space. **What you can do with it:** - Find treatment facilities near any US zip code within a configurable radius - Filter by level of care: detox, residential, IOP, outpatient, MAT - Get competitive density scores — how many facilities operate in a given market - Identify underserved markets by LOC type - Access verified data on 12,373 substance abuse facilities across all 50 states **Example prompts:** - "Find all IOP facilities within 25 miles of 75208" - "How many detox centers operate in the Dallas metro?" - "What levels of care are available in rural Wyoming?" - "Show me the top 10 markets with the fewest MAT providers" - "Is there a gap in residential treatment in Phoenix?" **Who it's for:** Treatment center operators doing competitive research, healthcare AI developers building patient navigation tools, and researchers studying treatment access gaps. **Endpoint:** https://gth-mcp-server.pages.dev/mcp
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 79.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1418 ms). |
| Protocol revision | 5/10 | Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 31/31 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 4 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 75% of peers
- This listing 84 · peer median 81
- Latency
- Faster than 46% of peers
- This listing 355 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Protocol revision −5
— Support the current protocol revision.
Now: Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/cbeggroup/gettreatmenthelp/mcpcurl -X POST https://server.smithery.ai/cbeggroup/gettreatmenthelp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'