Photon Health MCP by usefulapi
REMOTE · PHOTON-HEALTH.USEFULAPI.IO
Read Photon Health patients, prescriptions, orders, pharmacies and medications; screen interactions.
Available components
Last scanned (6 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1941 tokens (~92/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 13 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://photon-health.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of photon-health.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://photon-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://photon-health.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://photon-health.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://photon-health.usefulapi.io/mcp |
| Authorisation server | https://photon-health.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://photon-health.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/photon-health/ |
| http (plaintext) | http://photon-health.usefulapi.io/mcp | Inconclusive | 302 | http://photon-health.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
photonhealth_get_catalog Get a catalog ~54
Get one treatment catalog by id with its treatments and prescription templates (quantity, refills, days supply, directions). Photon GraphQL: catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_id | string | yes | Catalog id (from list_catalogs). |
No output schema declared.
No examples provided.
photonhealth_get_fill Get a fill ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fill_id | string | yes | Photon fill id (fil_…). |
No output schema declared.
No examples provided.
photonhealth_get_medication_by_ndc Look up a medication by NDC ~53
Find the medication matching a package NDC (11-digit National Drug Code). Photon GraphQL (clinical API): medicationFromNdc.
| Name | Type | Req | Description |
|---|---|---|---|
| package_ndc | string | yes | Package NDC. |
No output schema declared.
No examples provided.
photonhealth_get_order Get an order ~53
Get one order by id: state, patient, pharmacy, address, fulfillment status/tracking and its fills. Photon GraphQL: order.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | Photon order id (ord_…). |
No output schema declared.
No examples provided.
photonhealth_get_organization Get the organization ~44
Get the Photon organization these API keys belong to: id, name, type, NPI, address and contact details. Photon GraphQL (clinical API): organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
photonhealth_get_patient Get a patient ~57
Get one patient by Photon id, with allergies, medication history, preferred pharmacies, and their prescriptions and orders (ids + states). Photon GraphQL: patient.
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | string | yes | Photon patient id (pat_…). |
No output schema declared.
No examples provided.
photonhealth_get_pharmacy Get a pharmacy ~57
Get one pharmacy by Photon id: name, NPI, NCPDP, address, phone, fax and fulfillment types. Photon GraphQL: pharmacy.
| Name | Type | Req | Description |
|---|---|---|---|
| pharmacy_id | string | yes | Photon pharmacy id (phr_…). |
No output schema declared.
No examples provided.
photonhealth_get_prescription Get a prescription ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prescription_id | string | yes | Photon prescription id (rx_…). |
No output schema declared.
No examples provided.
photonhealth_list_catalogs List catalogs ~36
List the organization's treatment catalogs (the medications it prescribes) with their treatments and prescription templates. Photon GraphQL: catalogs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
photonhealth_list_dispense_units List dispense units ~40
List the dispense units Photon accepts on a prescription (e.g. Each, Milliliter, Tablet). Photon GraphQL: dispenseUnits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
photonhealth_list_medication_packages List medication packages ~58
List the packages (package NDCs) of a PRODUCT-level medication from list_medication_products. Photon GraphQL: medicationPackages.
| Name | Type | Req | Description |
|---|---|---|---|
| medication_id | string | yes | Medication id of a PRODUCT (from list_medication_products). |
No output schema declared.
No examples provided.
photonhealth_list_medication_products List medication products ~61
List the prescribable products (strength + form) of a DRUG-level medication from search_medications. Photon GraphQL: medicationProducts.
| Name | Type | Req | Description |
|---|---|---|---|
| medication_id | string | yes | Medication id of a DRUG concept (from search_medications). |
No output schema declared.
No examples provided.
photonhealth_list_orders List orders ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
photonhealth_list_patients List patients ~89
List the organization's patients (id, external id, name, date of birth, sex, contact, address), optionally filtered by name. Photon GraphQL: patients.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
photonhealth_list_prescriptions List prescriptions ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
photonhealth_list_users List users ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Filter by user name. |
| page_num | integer | – | Page number (1-based). |
| page_size | integer | – | Page size (default 50, max 100). |
No output schema declared.
No examples provided.
photonhealth_screen_interactions Screen for drug interactions ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| diagnosis_codes | array | – | Optional ICD-10 codes to screen against, e.g. ['I10']. |
| patient_id | string | yes | Photon patient id (pat_…). |
| treatment_ids | array | yes | Medication/treatment ids to screen (med_…, from search_medications or a catalog). |
No output schema declared.
No examples provided.
photonhealth_search_allergens Search allergens ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Allergen name, e.g. 'penicillin'. |
No output schema declared.
No examples provided.
photonhealth_search_medical_equipment Search medical equipment ~82
Search prescribable medical equipment/supplies (e.g. glucose test strips) by name. Photon GraphQL: medicalEquipment.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor: the id of the last item of the previous page. |
| first | integer | – | Page size (forward pagination). |
| name | string | – | Equipment name (partial). |
No output schema declared.
No examples provided.
photonhealth_search_medications Search medications ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
No output schema declared.
No examples provided.
photonhealth_search_pharmacies Search pharmacies ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
remote · photon-health.usefulapi.io
claude mcp add --transport http io-usefulapi-photon-health 'https://photon-health.usefulapi.io/mcp'
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.