Anpheros FHIR
Server Details
FHIR R4 health records for AI: people connect their own record with consent; free FHIR sandbox.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- anpheros/mcp-server
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- Anpheros Health
TDQS
Scored across 14 tools
Most tools target distinct actions (create, read, search, validate, list, reset). The get_patient_* family (context, summary, timeline, provenance) and list_patients vs search_fhir on Patient are the only mild overlaps, and the descriptions explicitly clarify boundaries (e.g. 'to filter use search_fhir on Patient'). create_patient vs create_fhir_resource is a minor convenience overlap but reasonably distinct.
Almost all names follow a consistent verb_noun snake_case pattern (create_fhir_resource, read_fhir_resource, get_patient_context, search_fhir, validate_fhir_resource). The only deviation is the noun-only sandbox_status, a small inconsistency that doesn't impede readability.
14 tools is well within the sweet spot for a FHIR sandbox server. Each tool covers a distinct capability (validation, creation, reading, search, import, context building, provenance, sandbox administration) and none feels redundant or padding.
Create, read, search, validate, import and context-building are all covered, but there is no update or delete operation for existing FHIR resources, which is a notable gap for a record-manipulation surface. Import and validation mitigate this partially, but agents cannot modify or remove records after creation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Your labs, wearables, DNA and notes as one health record your AI agent can read (OAuth 2.1).
Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.
Read patient-authorized EHR records: medications, labs, conditions, allergies. Consent-bounded.
Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides safe read-only access to synthetic healthcare data via FHIR R4, enabling AI assistants to search patients, retrieve vitals, and summarize conditions using a public sandbox.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI applications to securely search and manage healthcare data from FHIR R4-compliant servers with built-in safety validation for AI-generated clinical observations, preventing recording of physiologically impossible values.3 npm42 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceConnects frontier AI agents to HL7 FHIR R4 electronic health record repositories, enabling patient, observation, condition, medication, allergy, and diagnostic report queries plus draft-only clinical writes. Enforces mathematical safety gates, HIPAA-compliant tamper-evident audit logging, and token distillation of bulky FHIR payloads.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate and query clinically realistic synthetic health data with FHIR R4/R5 support and differential privacy.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.