io.usefulapi/metriport

REMOTE · METRIPORT.USEFULAPI.IO · SCANNED AUG 3

Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.

Available components

−51 this week 18 18 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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 returned HTTP 429. See how to fix → View diagnostics → Fail

Schema Quality & AI Usability0

Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified

Capabilities0

Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · metriport.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-metriport https://metriport.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-metriport]
url = "https://metriport.usefulapi.io/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add io-usefulapi-metriport --url https://metriport.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-metriport:
    url: "https://metriport.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-metriport": {
      "type": "http",
      "url": "https://metriport.usefulapi.io/mcp"
    }
  }
}

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

Changelog

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.

3 Aug 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
2 Aug 26 +55
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
1 Aug 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional

Show 5 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	17 Jul 2026	15 Oct 2026	ECDSA 256	ECDSA-SHA256	ba357601899e59000eedc95cf73e6234
SANs: usefulapi.io, metriport.usefulapi.io, *.metriport.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

DNSSEC insecure

Validation of metriport.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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	429

Header	Value
x-frame-options	SAMEORIGIN
referrer-policy	same-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://metriport.usefulapi.io/mcp	HTTP error	429
http (plaintext)	http://metriport.usefulapi.io/mcp	Inconclusive	429

MCP tools — 12 exposed · ~1,080 tokens

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.

Tool Tokens

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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}.

Input Output Examples

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.

Input Output Examples

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}.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	69
28 Jul	70
29 Jul	71
30 Jul	69
31 Jul	72
1 Aug	18
2 Aug	73
3 Aug	18