Metriport MCP by usefulapi
REMOTE · METRIPORT.USEFULAPI.IO
Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.1 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.1 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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 5 Nov 2026 · Probed https://metriport.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 metriport.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://metriport.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/metriport/ |
| http (plaintext) | http://metriport.usefulapi.io/mcp | Inconclusive | 302 | http://metriport.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 →
metriport_create_patient Create patient ~194
Creates a Patient in Metriport (writes PHI and initiates health-information-exchange queries). Medical API: POST /medical/v1/patient (facilityId is a required query param).
| Name | Type | Req | Description |
|---|---|---|---|
| address | array | yes | One or more addresses for the Patient. |
| contact | array | – | Optional contact info (phone / email). |
| dob | string | yes | Date of birth, yyyy-mm-dd. |
| facilityId | string | yes | REQUIRED. The Facility ID where the Patient receives care. |
| firstName | string | yes | The Patient's first name(s). |
| genderAtBirth | string | yes | Gender at birth: M, F, O (other), or U (unknown). |
| lastName | string | yes | The Patient's last name(s). |
| middleName | string | – | The Patient's middle name(s). |
| personalIdentifiers | array | – | Optional personal IDs (driver's license / SSN). |
No output schema declared.
No examples provided.
metriport_get_document_query_status Get document query status ~75
Check the progress/status of a Patient's document query (download + FHIR conversion counts). Medical API: POST /medical/v1/document/query with only patientId (no facilityId) returns current status without starting a new query.
| Name | Type | Req | Description |
|---|---|---|---|
| patientId | string | yes | The Patient ID whose document-query status to check. |
No output schema declared.
No examples provided.
metriport_get_document_url Get document download URL ~97
Get a temporary, downloadable URL for a document by its file name (optionally converting XML/CDA to html or pdf). Medical API: GET /medical/v1/document/download-url.
| Name | Type | Req | Description |
|---|---|---|---|
| conversionType | string | – | Optional doc type to convert to, e.g. pdf, html, xml (for XML/CDA files). |
| fileName | string | yes | The file name of the document (from metriport_list_documents). |
No output schema declared.
No examples provided.
metriport_get_facility Get facility ~49
Get a single Facility by its Metriport ID. Medical API: GET /medical/v1/facility/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Metriport Facility ID. |
No output schema declared.
No examples provided.
metriport_get_medical_record_summary Get medical record summary ~76
Get a URL to the Patient's medical record summary rendered as pdf or html. Medical API: GET /medical/v1/patient/{patientId}/medical-record.
| Name | Type | Req | Description |
|---|---|---|---|
| conversionType | string | yes | The format to render: pdf or html. |
| patientId | string | yes | The Metriport Patient ID. |
No output schema declared.
No examples provided.
metriport_get_patient Get patient ~53
Get a single Patient by its Metriport ID (demographics + facility IDs). Medical API: GET /medical/v1/patient/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Metriport Patient ID. |
No output schema declared.
No examples provided.
metriport_list_consolidated_queries List consolidated queries ~58
Get the status of the Patient's consolidated-data (FHIR) queries. Medical API: GET /medical/v1/patient/{id}/consolidated/query.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Metriport Patient ID. |
No output schema declared.
No examples provided.
metriport_list_documents List documents ~109
List the document references currently available for a Patient at Metriport (optionally filtered by date range and content search). Medical API: GET /medical/v1/document.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Text to search within the document reference and contents (min 3 chars). |
| dateFrom | string | – | Inclusive start date yyyy-mm-dd. |
| dateTo | string | – | Inclusive end date yyyy-mm-dd. |
| patientId | string | yes | The Patient ID whose available documents to list. |
No output schema declared.
No examples provided.
metriport_list_facilities List facilities ~42
List all Facilities under your Metriport Organization (id, name, npi, address). Medical API: GET /medical/v1/facility.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metriport_list_patients List patients ~62
List Patients — all Patients, or only those at a given Facility if facilityId is supplied. Medical API: GET /medical/v1/patient.
| Name | Type | Req | Description |
|---|---|---|---|
| facilityId | string | – | Optional Facility ID to filter by. Omit to list all patients. |
No output schema declared.
No examples provided.
metriport_start_consolidated_query Start consolidated query ~156
Starts a consolidated-data (FHIR) query for the patient. Returns a requestId; the bundle is delivered asynchronously (webhook). Medical API: POST /medical/v1/patient/{id}/consolidated/query.
| Name | Type | Req | Description |
|---|---|---|---|
| conversionType | string | – | Output format: json, pdf, or html. |
| dateFrom | string | – | Inclusive start date yyyy-mm-dd. |
| dateTo | string | – | Inclusive end date yyyy-mm-dd. |
| id | string | yes | The Metriport Patient ID. |
| metadata | object | – | Optional custom string key-value pairs returned in the webhook. |
| resources | string | – | Comma-separated, case-sensitive list of FHIR resource types. Omit for all. |
No output schema declared.
No examples provided.
metriport_start_document_query Start document query ~109
Starts a document query — retrieves the patient's medical documents from connected HIE networks. Returns a requestId; results arrive asynchronously. Medical API: POST /medical/v1/document/query (patientId and facilityId are required query params).
| Name | Type | Req | Description |
|---|---|---|---|
| facilityId | string | yes | REQUIRED. The Facility ID where the patient receives care. |
| metadata | object | – | Optional custom string key-value pairs returned in the webhook. |
| patientId | string | yes | REQUIRED. The Patient ID to query documents for. |
No output schema declared.
No examples provided.
How do I install the Metriport MCP by usefulapi server?
Metriport MCP by usefulapi is a hosted endpoint at https://metriport.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 · metriport.usefulapi.io
claude mcp add --transport http io-usefulapi-metriport 'https://metriport.usefulapi.io/mcp'
What is the Metriport MCP by usefulapi server?
Metriport MCP by usefulapi is listed in the public MCP registry as io.usefulapi/metriport. Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport. This page covers its hosted endpoint (https://metriport.usefulapi.io/mcp).
Is the Metriport MCP by usefulapi server safe to use?
Metriport MCP by usefulapi scores 18 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 Metriport MCP by usefulapi server expose?
Metriport MCP by usefulapi exposes 12 tools: metriport_list_facilities, metriport_get_facility, metriport_list_patients, metriport_get_patient, metriport_list_documents, and 7 more. Their descriptions and schemas cost roughly 1,080 tokens of context every time the server is loaded.
Does the Metriport MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Metriport MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Metriport MCP by usefulapi server still maintained?
Metriport MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Metriport MCP by usefulapi server?
VerifyMCP ran 4 checks on Metriport MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Metriport MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.