Healthpoint MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEALTHPOINT_API_KEY | Yes | Your Healthpoint API key. | |
| HEALTHPOINT_BASE_URL | No | Base URL for the Healthpoint API. Default is https://uat.healthpointapi.com/baseR4/ | https://uat.healthpointapi.com/baseR4/ |
| HEALTHPOINT_AUTH_SCHEME | No | Authentication scheme: bearer, x-api-key, header:<name>, or none. Default is x-api-key. | x-api-key |
| HEALTHPOINT_TIMEOUT_SECS | No | Timeout in seconds for API requests. Default is 30. | 30 |
| HEALTHPOINT_EXPORT_POLICY | No | Export policy: local-only, licensed-share, or open-approved. Default is local-only. | local-only |
| HEALTHPOINT_GEO_SEARCH_MODE | No | Geographic search mode: healthpoint-lat-lon or fhir-near. Default is healthpoint-lat-lon. | healthpoint-lat-lon |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthpoint_access_policyA | Show conservative Healthpoint access/export policy. Use before exporting or reusing data. |
| healthpoint_api_access_notesA | Show Healthpoint API access notes discovered from the portal. Does not include secrets. |
| healthpoint_diagnostic_statusA | Show redacted Healthpoint client configuration and readiness. Never returns the API key. |
| healthpoint_find_nearby_servicesA | Find nearby Healthpoint HealthcareService records by latitude/longitude. Read-only. |
| healthpoint_get_locationB | Get a single Healthpoint Location record by FHIR id. Read-only. |
| healthpoint_get_organizationA | Get a single Healthpoint Organization record by FHIR id. Read-only. |
| healthpoint_get_serviceA | Get a single Healthpoint HealthcareService record by FHIR id. Read-only. |
| healthpoint_read_resource_uriA | Read a supported healthpoint:// resource URI. This mirrors planned MCP resources while keeping the operation explicit and read-only. |
| healthpoint_search_by_snomedA | Search Healthpoint HealthcareService records by SNOMED CT code. Read-only. |
| healthpoint_search_servicesB | Search Healthpoint HealthcareService records. Read-only; requires a user-provided API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| healthpoint_license_check | Prepare a license/export safety check before using Healthpoint data. |
| healthpoint_safe_search | Draft a safe Healthpoint service-search request using licensed, read-only access. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Diagnostic status | Redacted runtime client configuration |
| API access notes | Non-secret Healthpoint API endpoint and access notes |
| Access policy | Conservative Healthpoint access and export policy |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: policy display, API notes, diagnostic status, nearby search, individual record retrieval for location/organization/service, URI reading, SNOMED search, and general search. No overlapping functionality.
All tools follow a consistent 'healthpoint_' prefix with snake_case verb_noun pattern (e.g., find_nearby_services, get_location). No mixing of conventions.
With 10 tools covering metadata, search, and retrieval for a healthcare data domain, the count is well-scoped. Each tool serves a specific purpose without redundancy or bloat.
The tool set covers all necessary read-only operations for Healthpoint data: metadata about access and diagnostics, searching by proximity and SNOMED, retrieving individual resources, and parsing URIs. As a read-only server, there are no missing write operations.