# Photon Health MCP by usefulapi (remote · photon-health.usefulapi.io)

Read Photon Health patients, prescriptions, orders, pharmacies and medications; screen interactions.

- Trust score: 67/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `photon-health.usefulapi.io`: 67/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-photon-health/photon-health.md), [page](https://verifymcp.io/servers/io-usefulapi-photon-health/photon-health)

## Channel facts

- Endpoint: `https://photon-health.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1941 tokens (~92/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Photon Health MCP by usefulapi server?

Photon Health MCP by usefulapi is a hosted endpoint at https://photon-health.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-photon-health 'https://photon-health.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-photon-health": {
      "url": "https://photon-health.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-photon-health": {
      "type": "http",
      "url": "https://photon-health.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-photon-health]
url = "https://photon-health.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-photon-health": {
      "type": "remote",
      "url": "https://photon-health.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-photon-health --url 'https://photon-health.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-photon-health:
    url: "https://photon-health.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-photon-health": {
      "Transport": "http",
      "Url": "https://photon-health.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-photon-health -t streamable-http -u 'https://photon-health.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-photon-health": {
      "type": "http",
      "url": "https://photon-health.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 64, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.4.0 → 1.5.0

### 2026-10-12 (score 62, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 61)

First indexed and scored.

## MCP tools (21)

### `photonhealth_list_patients` (~89 tokens)

List patients

List the organization's patients (id, external id, name, date of birth, sex, contact, address), optionally filtered by name. Photon GraphQL: patients.

Input parameters:

- `after` (string): Cursor: the id of the last item of the previous page.
- `first` (integer): Page size (forward pagination).
- `name` (string): Filter by patient name (partial match).

### `photonhealth_get_patient` (~57 tokens)

Get a patient

Get one patient by Photon id, with allergies, medication history, preferred pharmacies, and their prescriptions and orders (ids + states). Photon GraphQL: patient.

Input parameters:

- `patient_id` (string, required): Photon patient id (pat_…).

### `photonhealth_list_prescriptions` (~152 tokens)

List prescriptions

List the organization's prescriptions, filterable by patient, prescriber and state (ACTIVE, EXPIRED, DEPLETED, CANCELED). Each has the medication, quantity, refills/fills remaining, directions, diagnoses and fills. Photon GraphQL: prescriptions.

Input parameters:

- `after` (string): Cursor: the id of the last item of the previous page.
- `first` (integer): Page size (forward pagination).
- `patient_id` (string): Only this patient's prescriptions (pat_…).
- `patient_name` (string): Filter by patient name.
- `prescriber_id` (string): Only prescriptions written by this prescriber (Photon user id).
- `state` (string): Prescription state.

### `photonhealth_get_prescription` (~76 tokens)

Get a prescription

Get one prescription by id: state, prescriber, patient, medication (with RxCUI/NDC codes), quantity, refills and fills remaining, days supply, directions, notes, diagnoses, dates and fills. Photon GraphQL: prescription.

Input parameters:

- `prescription_id` (string, required): Photon prescription id (rx_…).

### `photonhealth_list_orders` (~137 tokens)

List orders

List pharmacy orders, filterable by patient and state (ROUTING, PENDING, PLACED, COMPLETED, CANCELED, ERROR). Each has the pharmacy, delivery address, fulfillment (type, state, carrier, tracking number) and fills. Photon GraphQL: orders.

Input parameters:

- `after` (string): Cursor: the id of the last item of the previous page.
- `first` (integer): Page size (forward pagination).
- `patient_id` (string): Only this patient's orders (pat_…).
- `patient_name` (string): Filter by patient name.
- `state` (string): Order state.

### `photonhealth_get_order` (~53 tokens)

Get an order

Get one order by id: state, patient, pharmacy, address, fulfillment status/tracking and its fills. Photon GraphQL: order.

Input parameters:

- `order_id` (string, required): Photon order id (ord_…).

### `photonhealth_get_fill` (~73 tokens)

Get a fill

Get one fill (a single dispensing of a prescription within an order) by id: state (SCHEDULED, NEW, SENT, CANCELED), requested/filled times, medication, prescription and order. Photon GraphQL: fill.

Input parameters:

- `fill_id` (string, required): Photon fill id (fil_…).

### `photonhealth_search_pharmacies` (~156 tokens)

Search pharmacies

Search pharmacies by name and/or near a location (latitude/longitude + radius in miles), by fulfillment type (PICK_UP = retail, MAIL_ORDER). Returns NPI, NCPDP, address, phone, fax. Photon GraphQL: pharmacies.

Input parameters:

- `first` (integer): Page size (forward pagination).
- `latitude` (number): Search center latitude.
- `longitude` (number): Search center longitude.
- `name` (string): Pharmacy name (partial).
- `offset` (integer): Number of results to skip (offset pagination).
- `radius_miles` (integer): Search radius in miles (with latitude/longitude).
- `type` (string): Fulfillment type (Photon's default is PICK_UP).

### `photonhealth_get_pharmacy` (~57 tokens)

Get a pharmacy

Get one pharmacy by Photon id: name, NPI, NCPDP, address, phone, fax and fulfillment types. Photon GraphQL: pharmacy.

Input parameters:

- `pharmacy_id` (string, required): Photon pharmacy id (phr_…).

### `photonhealth_search_medications` (~140 tokens)

Search medications

Search Photon's medication database by drug name (partial) or code (RxCUI, NDC or SKU). Returns DRUG-level concepts with RxCUI/NDC codes, schedule, controlled flag, strength and form; drill down with list_medication_products / list_medication_packages. Photon GraphQL: medications.

Input parameters:

- `after` (string): Cursor: the id of the last item of the previous page.
- `code` (string): RxCUI, NDC or SKU.
- `first` (integer): Page size (forward pagination).
- `name` (string): Drug name (partial), e.g. 'amoxicillin'.

### `photonhealth_list_medication_products` (~61 tokens)

List medication products

List the prescribable products (strength + form) of a DRUG-level medication from search_medications. Photon GraphQL: medicationProducts.

Input parameters:

- `medication_id` (string, required): Medication id of a DRUG concept (from search_medications).

### `photonhealth_list_medication_packages` (~58 tokens)

List medication packages

List the packages (package NDCs) of a PRODUCT-level medication from list_medication_products. Photon GraphQL: medicationPackages.

Input parameters:

- `medication_id` (string, required): Medication id of a PRODUCT (from list_medication_products).

### `photonhealth_get_medication_by_ndc` (~53 tokens)

Look up a medication by NDC

Find the medication matching a package NDC (11-digit National Drug Code). Photon GraphQL (clinical API): medicationFromNdc.

Input parameters:

- `package_ndc` (string, required): Package NDC.

### `photonhealth_search_medical_equipment` (~82 tokens)

Search medical equipment

Search prescribable medical equipment/supplies (e.g. glucose test strips) by name. Photon GraphQL: medicalEquipment.

Input parameters:

- `after` (string): Cursor: the id of the last item of the previous page.
- `first` (integer): Page size (forward pagination).
- `name` (string): Equipment name (partial).

### `photonhealth_list_catalogs` (~36 tokens)

List catalogs

List the organization's treatment catalogs (the medications it prescribes) with their treatments and prescription templates. Photon GraphQL: catalogs.

### `photonhealth_get_catalog` (~54 tokens)

Get a catalog

Get one treatment catalog by id with its treatments and prescription templates (quantity, refills, days supply, directions). Photon GraphQL: catalog.

Input parameters:

- `catalog_id` (string, required): Catalog id (from list_catalogs).

### `photonhealth_search_allergens` (~65 tokens)

Search allergens

Search Photon's allergen list by name (fuzzy), e.g. to map a patient's reported allergy to an allergen id/RxCUI. Photon GraphQL: allergens.

Input parameters:

- `name` (string, required): Allergen name, e.g. 'penicillin'.

### `photonhealth_list_dispense_units` (~40 tokens)

List dispense units

List the dispense units Photon accepts on a prescription (e.g. Each, Milliliter, Tablet). Photon GraphQL: dispenseUnits.

### `photonhealth_get_organization` (~44 tokens)

Get the organization

Get the Photon organization these API keys belong to: id, name, type, NPI, address and contact details. Photon GraphQL (clinical API): organization.

### `photonhealth_list_users` (~97 tokens)

List users

List the organization's users (prescribers and staff): id, name, email, NPI, credentials and roles — use an id as prescriber_id in list_prescriptions. Photon GraphQL (clinical API): users.

Input parameters:

- `name` (string): Filter by user name.
- `page_num` (integer): Page number (1-based).
- `page_size` (integer): Page size (default 50, max 100).

### `photonhealth_screen_interactions` (~161 tokens)

Screen for drug interactions

Screen proposed medications for a patient against drug-drug and drug-allergy (and diagnosis) interactions, using the patient's allergies, medication history and existing prescriptions. READ-ONLY: nothing is written or prescribed. Returns alerts with type (DRUG, ALLERGEN, CONDITION), severity (MINOR, MODERATE, MAJOR), a description and the involved medications/allergens. Photon GraphQL (clinical API): prescriptionScreen.

Input parameters:

- `diagnosis_codes` (array): Optional ICD-10 codes to screen against, e.g. ['I10'].
- `patient_id` (string, required): Photon patient id (pat_…).
- `treatment_ids` (array, required): Medication/treatment ids to screen (med_…, from search_medications or a catalog).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-photon-health/photon-health#diagnostics

## Score history

- 2026-10-18: 67
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 65
- 2026-10-14: 65
- 2026-10-13: 64
- 2026-10-12: 62
- 2026-10-10: 61

## Common questions

### What is the Photon Health MCP by usefulapi server?

Photon Health MCP by usefulapi is listed in the public MCP registry as io.usefulapi/photon-health. Read Photon Health patients, prescriptions, orders, pharmacies and medications; screen interactions. This page covers its hosted endpoint (https://photon-health.usefulapi.io/mcp).

### Is the Photon Health MCP by usefulapi server safe to use?

Photon Health MCP by usefulapi scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Photon Health MCP by usefulapi server expose?

Photon Health MCP by usefulapi exposes 21 tools: photonhealth_list_patients, photonhealth_get_patient, photonhealth_list_prescriptions, photonhealth_get_prescription, photonhealth_list_orders, and 16 more. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.

### Does the Photon Health MCP by usefulapi server require authentication?

Yes. Photon Health MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Photon Health MCP by usefulapi server still maintained?

Photon Health MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://photon-health.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/photon-health/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-photon-health/photon-health.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-photon-health/photon-health.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-photon-health/photon-health