# Usefulapi Metriport MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.usefulapi%2Fmetriport
Registry id: `mcp-registry/io.usefulapi/metriport`
Status: auth-required (checked 2026-10-27T13:52:47.313Z)

## Verdict

Usefulapi Metriport MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 64 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 12 tools, costing an agent about 2,295 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 64 ms | 88% of MCP servers |
| p95 handshake latency | 304 ms | — |
| Checks in 30 days | 224 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~2,295 tokens | 50% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

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

## Tools (12)

- `metriport_create_patient`: Creates a Patient in Metriport (writes PHI and initiates health-information-exchange queries). Medical API: POST /medical/v1/patient (facilityId is a required q
- `metriport_get_document_query_status`: Check the progress/status of a Patient's document query (download + FHIR conversion counts). Medical API: POST /medical/v1/document/query with only patientId (n
- `metriport_get_document_url`: 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
- `metriport_get_facility`: Get a single Facility by its Metriport ID. Medical API: GET /medical/v1/facility/{id}.
- `metriport_get_medical_record_summary`: Get a URL to the Patient's medical record summary rendered as pdf or html. Medical API: GET /medical/v1/patient/{patientId}/medical-record.
- `metriport_get_patient`: Get a single Patient by its Metriport ID (demographics + facility IDs). Medical API: GET /medical/v1/patient/{id}.
- `metriport_list_consolidated_queries`: Get the status of the Patient's consolidated-data (FHIR) queries. Medical API: GET /medical/v1/patient/{id}/consolidated/query.
- `metriport_list_documents`: List the document references currently available for a Patient at Metriport (optionally filtered by date range and content search). Medical API: GET /medical/v1
- `metriport_list_facilities`: List all Facilities under your Metriport Organization (id, name, npi, address). Medical API: GET /medical/v1/facility.
- `metriport_list_patients`: List Patients — all Patients, or only those at a given Facility if facilityId is supplied. Medical API: GET /medical/v1/patient.
- `metriport_start_consolidated_query`: Starts a consolidated-data (FHIR) query for the patient. Returns a requestId; the bundle is delivered asynchronously (webhook). Medical API: POST /medical/v1/pa
- `metriport_start_document_query`: Starts a document query — retrieves the patient's medical documents from connected HIE networks. Returns a requestId; results arrive asynchronously. Medical API

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.