What can you do with this server?

This server provides AI agents with structured access to a curated directory of 12,338 US addiction treatment facilities sourced from SAMHSA, enabling facility discovery and research across all 50 states. Here's what you can do: * Search for treatment facilities: Find addiction treatment centers by US state (required), city, treatment type (e.g., Inpatient Rehab, Detox, IOP, PHP, MAT, Counseling, Sober Living, Outpatient), and insurance accepted (e.g., Medicaid, Medicare, Aetna, Blue Cross, Private Pay). Results include facility names, locations, programs, insurance info, phone numbers, and browse URLs. * Get detailed facility profiles: Retrieve the full profile of a specific facility by name, including address, phone, programs offered, insurance plans accepted, SAMHSA verification status, and a direct browse URL. * List states with coverage: Get all US states (+ DC) that have facility data along with per-state facility counts — useful for exploring coverage before searching. * Look up treatment type definitions: Get detailed explanations of all treatment program types (duration, intensity, typical fit) to help understand which treatment type to search for.

GTH Intelligence - Substance Abuse Treatment Finder

by Crindo2

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Remote

GTH Intelligence - Substance Abuse Treatment Finder

An MCP server that gives AI agents access to 12,338 curated US addiction treatment facilities, sourced from SAMHSA, across all 50 states. Built for treatment operators, healthcare AI developers, and anyone building tools that help people find care.

What It Does

The GTH Intelligence MCP server provides structured access to GetTreatmentHelp's directory of addiction treatment facilities -- enriched with descriptions, phone numbers, websites, programs offered, and insurance accepted.

Related MCP server: GPH Intelligence - Healthcare Vendor Finder

Tools

`search_facilities`

Search for addiction treatment facilities. Filter by US state (required), city, treatment type, and insurance accepted. Returns facility names, locations, programs, insurance, phone numbers, and a browse URL.

Parameters:

state (required) -- US state name or two-letter abbreviation (e.g. "California" or "CA")
city -- City name (partial match supported)
treatment_type -- One of: Inpatient Rehab, Outpatient, Detox, IOP (Intensive Outpatient), PHP (Partial Hospitalization), MAT (Medication-Assisted Treatment), Counseling, Sober Living
insurance -- Insurance provider accepted (e.g. "Medicaid", "Aetna", "Medicare")
limit -- Max results to return (1-20, default 5)

`get_facility_detail`

Get the full profile of one treatment facility by name: location, phone, programs offered, insurance accepted, and a browse URL. Partial name matching supported.

Parameters:

name (required) -- Full or partial facility name

`list_states`

List every US state with treatment facility data, with per-state facility counts.

`get_treatment_types`

Get definitions of all treatment program types (Inpatient Rehab, Detox, PHP, IOP, Outpatient, MAT, Counseling, Sober Living) with duration, intensity, and typical fit.

Usage

MCP Endpoint

https://gth-mcp-server.pages.dev/mcp

Connect via Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "gth-intelligence": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gth-mcp-server.pages.dev/mcp"]
    }
  }
}

No API key required.

Data Coverage

12,338 curated addiction treatment facilities, sourced from SAMHSA
All 50 states + DC
Programs, insurance accepted, phone numbers, and browse links per facility
Monthly data refreshes from SAMHSA

Use Cases

Help people find nearby treatment options
Build facility-finder features into healthcare apps
Power competitive intelligence tools for treatment operators
Research treatment availability by geography or program type

API Access

Free: 100 calls per IP per day, no API key required.

For higher-volume access, get in touch via gettreatmenthelp.com/api-access/

Troubleshooting

No results returned -- state is required for search_facilities, so make sure it is set; then broaden by removing the city/treatment_type/insurance filters or trying a different state. Call list_states to see where coverage exists.
HTTP 429 (rate limited) -- the free tier allows 100 calls per IP per day, resetting at 00:00 UTC. For higher volume, see API Access above.
Can't connect -- point your client at the remote endpoint, no API key required:
```
npx -y mcp-remote https://gth-mcp-server.pages.dev/mcp
```
403 from a browser -- the /mcp endpoint validates the Origin header to prevent DNS rebinding. Standard MCP clients (Claude Desktop, mcp-remote, server-to-server) send no Origin header and connect fine; only disallowed browser origins are blocked.
Support -- questions or higher-volume access requests: cbeggroup@gmail.com

License

MIT

Available Tools

4 tools

get_facility_detailGet Facility DetailA

Read-onlyIdempotent

Inspect

Get the full profile of one specific treatment facility: address, phone, programs offered, insurance plans accepted, SAMHSA verification status, and a direct browse URL. Supports partial name matching — returns the best match if multiple facilities contain the query string. Use after search_facilities when the user wants to drill into a named facility.

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes	Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true and idempotentHint=true, indicating a safe, idempotent read operation. The description adds transparency by disclosing partial name matching and best match behavior, which is beyond what annotations provide. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the tool's purpose and what it returns, followed by a brief note on matching behavior and usage context. No fluff; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one simple parameter, rich annotations, and a clear description of return values (even without an output schema), the description is complete. It covers purpose, behavior, usage context, and data details sufficiently for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter 'name' with full schema description coverage (100%), so the baseline is 3. The description in the schema already explains the parameter well. The main description adds little beyond the schema for parameter meaning, but it does mention partial matching behavior which is marginally useful.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves the full profile of one specific treatment facility, listing specific attributes (address, phone, programs, insurance, SAMHSA status, browse URL). It distinguishes from sibling tools by explicitly saying to use after search_facilities for drilling into a named facility.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly mentions when to use: 'Use after search_facilities when the user wants to drill into a named facility.' It also notes partial name matching and best match behavior. While it doesn't explicitly list when not to use, the guidance is clear and contextual.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_treatment_typesGet Treatment Type DefinitionsA

Read-onlyIdempotent

Inspect

Get definitions of all treatment program types (Inpatient Rehab, Detox, PHP, IOP, Outpatient, MAT, Counseling, Sober Living) with duration, intensity, and typical fit. Returns markdown-formatted explanations. Use when the user is uncertain which treatment_type to pass to search_facilities, or asks 'what's the difference between X and Y'.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint. Description adds that it returns markdown-formatted explanations, providing additional behavioral detail beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: first states core purpose and output, second provides usage guidance. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully explains what the tool returns (definitions, types, format) and when to use it. No missing details given zero parameters and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; schema coverage is 100% (empty). Baseline for 0 parameters is 4. Description properly omits parameter info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the specific verb 'Get' and resource 'definitions of all treatment program types', listing example types and output format. Distinguished from siblings which deal with facilities, states, and search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use: when uncertain about treatment_type for search_facilities or when user asks about differences between types. Provides clear context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_statesList States with CoverageA

Read-onlyIdempotent

Inspect

List every US state that has treatment facility data in this directory, with per-state facility counts. Returns an array of {state, stateAbbr, count}. Use as a first step when the user's location is unclear, or to discover where coverage exists before calling search_facilities.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only and idempotent; description adds value by specifying output structure (array of {state, stateAbbr, count}) and coverage context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with front-loaded purpose and immediate use guidance, no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a zero-parameter tool with good annotations; covers purpose, usage, and output format without gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters; baseline score of 4 applies as description does not need to add param info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists US states with treatment facility data and per-state counts, distinguishing it from sibling tools like search_facilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly recommends using it as a first step when location is unclear or before calling search_facilities, providing clear usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_facilitiesSearch Treatment FacilitiesA

Read-onlyIdempotent

Inspect

Search the 12,338 curated, SAMHSA-sourced US addiction treatment facility directory by state, city, treatment type, and insurance. Returns matched facilities with name, city/state, programs offered, insurance accepted, phone, and browse URL. Use this to find candidates — then call get_facility_detail for one facility's full profile. If the user is uncertain about location coverage, call list_states first.

ParametersJSON Schema

Name	Required	Description
`state`	Yes	US state name or 2-letter abbreviation (e.g. "California" or "CA"). Required — searches are scoped to one state at a time.
`city`	No	City name (partial match supported — 'san fran' matches 'San Francisco')
`treatment_type`	No	Type of treatment program. Call get_treatment_types if the user is unsure which applies.
`insurance`	No	Insurance provider accepted (e.g. "Medicaid", "Aetna", "Blue Cross", "Medicare", "Private Pay"). Partial match supported.
`limit`	No	Max results to return (1-20, default 5)

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds behavioral context by specifying the search scope (state required, optional other filters) and what the response includes (matched facilities with fields listed). It does not contradict annotations and adds useful information about the tool's non-destructive, idempotent nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences covering purpose and usage plus a one-sentence cross-reference to sibling tools. Front-loading the key action and output, with zero filler. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters (1 required) and no output schema, the description is sufficiently complete. It explains the tool's purpose, output fields, required state parameter, and links to sibling tools. However, it does not mention default limit behavior (schema covers this) nor pagination, but those are minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for all 5 parameters. The description summarizes the parameter usage but does not add significant new meaning beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting; the description provides high-level context without enriching parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches a curated SAMHSA-sourced directory of 12,338 US addiction treatment facilities by state, city, treatment type, and insurance, and lists what it returns (name, city/state, programs, insurance, phone, browse URL). It also explicitly distinguishes from siblings by directing to get_facility_detail for full profiles and list_states for location coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: 'Search the directory... Use this to find candidates — then call get_facility_detail for one facility's full profile.' It also tells when to use alternatives: 'If the user is uncertain about location coverage, call list_states first' and implicitly references get_treatment_types for treatment type uncertainty.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesJun 20, 2026
- First observedget_facility_detail
- First observedget_treatment_types
- First observedlist_states
- First observedsearch_facilities

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: listing states, searching facilities, getting facility details, and explaining treatment types. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_states, search_facilities).

Tool Count5/5

Four tools is ideal for a directory finder: coverage discovery, search, detail, and terminology help. Each tool earns its place.

Completeness5/5

The set covers the full workflow: discover coverage (list_states), search with filters (search_facilities), retrieve full profile (get_facility_detail), and understand program types (get_treatment_types). No obvious gaps.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

SAMHSA Treatment Locator
com.olyport
Find substance abuse and mental health treatment facilities
Government Data Health & Wellness Search
2
ChooseHelp Treatment Directory A
com.choosehelp
Editorially independent addiction & mental-health directory — facilities, therapists, expert Q&A.
Health & Wellness Search
91
GPH Intelligence - Healthcare Vendor Finder A
io.github.Crindo2
Find 76,000+ curated healthcare service vendors across 25 categories and all 50 US states.
Health & Wellness Search Research & Data
42
Bezal — Local Business Intelligence for AI Agents B
ai.bezal
Search 7,000+ local service businesses across America by category, location, or keyword.
Search E-commerce & Retail Location Services
132

Related MCP Servers

rollin-mcp-server
Search Location Services
DavidSirota
A
license
A
quality
C
maintenance
Wheelchair accessibility data for 105,000+ locations across 15 US states. Enables search, details, and feedback submission through natural language.
Updated 18 days ago (2026-08-22 01:17 UTC)
5
81
1
MIT
GPH Intelligence - Healthcare
Search
Crindo2
A
license
A
quality
B
maintenance
Find 76,000+ curated healthcare service vendors across 25 categories and all 50 US states. Search by category, specialty, city, state, and EHR system to identify billing, credentialing, EHR, and practice-consulting vendors that serve medical practices.
Updated a month ago (2026-08-08 00:49 UTC)
3
MIT
Formulary MCP Server
Biology & Medicine Government Data
openpharma-org
F
license
Not graded
quality
C
maintenance
Provides unified access to drug formulary data from US ACA marketplace health insurance plans, enabling drug search, coverage details, restriction info, and plan comparison across thousands of plans.
Updated 9 months ago (2025-12-22 17:50 UTC)
-
GLP1Search MCP Server
Health & Wellness Search Biology & Medicine
Sndevore77
A
license
Not graded
quality
C
maintenance
Enables searching and comparing GLP-1 medication providers, medications, side effects, and FAQs across a directory of 18,344 US clinics, telehealth programs, and pharmacies.
Updated a month ago (2026-07-30 18:37 UTC)
32
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crindo2/gth-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

GTH Intelligence - Substance Abuse Treatment Finder

What It Does

Tools

search_facilities

get_facility_detail

list_states

get_treatment_types

Usage

MCP Endpoint

Connect via Claude Desktop

Data Coverage

Use Cases

API Access

Troubleshooting

Links

License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`search_facilities`

`get_facility_detail`

`list_states`

`get_treatment_types`