Anpheros FHIR

com.anpherosPublished by anpheros.comOfficial publisherv0.3.0Updated Oct 26, 2026

HL7 FHIR R4 health-data API for AI agents: free sandbox, 30 synthetic patients, AI-ready context.

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote MCP endpoint exposing an HL7 FHIR R4 health-data API, with a free sandbox of 30 synthetic patients for AI agents.

What you can do
  • Connect an assistant to an HL7 FHIR R4 health-data API through a hosted remote endpoint.
  • Work with FHIR resources for a sandbox dataset of 30 synthetic patients.
  • Use AI-ready context from the health-data API in assistant workflows.
  • Authenticate either with OAuth or, for developers, an optional sandbox API key.
When to use it
Useful when you want an assistant to explore or prototype against FHIR R4 health data without standing up your own FHIR server, especially for testing with synthetic patients in the free sandbox.
Requirements
A remote streamable HTTP endpoint at platform.anpheros.com; no local package or runtime. OAuth authentication is required for normal use; developers may instead supply an optional sandbox API key in the X-API-Key header. Network access to the hosted platform.
Before you install
The endpoint handles health data, so treat anything beyond the synthetic sandbox as sensitive. The X-API-Key header carries a secret sandbox key and should not be shared. The manifest lists no tools, so confirm what operations the server exposes before relying on it.

Installation

In SourceWeft

  1. Open Anpheros FHIR in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.anpheros%2Ffhir/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "anpheros-fhir": {
      "type": "http",
      "url": "https://platform.anpheros.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.3.0LatestOct 16, 2026
  2. v0.2.0Oct 11, 2026
  3. v0.1.0Oct 11, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.