Metriport MCP by usefulapi
io.usefulapi/metriportusefulapi.iostreamable-httpv1.41.0Scanned
Read and write patients, facilities, medical documents, and consolidated FHIR records in Metriport.
12 tools: 3 can delete or cancel things and 9 only read.
- Reads private data · 3
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Metriport MCP by usefulapi can do
The Metriport MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (3 tools: metriport_create_patient, metriport_start_document_query and metriport_start_consolidated_query). 9 tools only read.
3 tools read private data (metriport_list_documents, metriport_get_document_query_status and metriport_get_document_url); 2 tools bring in text other people can write (metriport_get_document_url and metriport_get_medical_record_summary).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.41.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Deletes or cancels 3Claude Code: deny
metriport_create_patientCreates a Patient in Metriport (writes PHI and initiates health-information-exchange queries).No findings
Why it is in this group
- The name "metriport_create_patient" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Create patient
- destructiveHint: true
metriport_start_consolidated_queryStarts a consolidated-data (FHIR) query for the patient.No findings
Why it is in this group
- The name "metriport_start_consolidated_query" says "start": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Start consolidated query
- destructiveHint: true
metriport_start_document_queryStarts a document query — retrieves the patient's medical documents from connected HIE networks.No findings
Why it is in this group
- The name "metriport_start_document_query" says "start": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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).
Annotations the server declares
- title: Start document query
- destructiveHint: true
Only reads 9Show 9 read-only tools
metriport_get_document_query_statusCheck the progress/status of a Patient's document query (download + FHIR conversion counts).Reads private dataNo findings
Why it is in this group
- The name "metriport_get_document_query_status" says "get": a word for reading.
What it can reach
- private-dataThe name "metriport_get_document_query_status" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get document query status
- readOnlyHint: true
metriport_get_document_urlGet a temporary, downloadable URL for a document by its file name (optionally converting XML/CDA to html or pdf).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "metriport_get_document_url" says "get": a word for reading.
What it can reach
- private-dataThe name "metriport_get_document_url" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "get" and "document": it reads documents.
- private-dataThe input names a file (input.fileName), and the tool reads: it reads files.
- untrusted-inputThe name "metriport_get_document_url" says "get" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get document download URL
- readOnlyHint: true
metriport_get_facilityGet a single Facility by its Metriport ID.No findings
Why it is in this group
- The name "metriport_get_facility" says "get": a word for reading.
Description, as the server wrote it Get a single Facility by its Metriport ID. Medical API: GET /medical/v1/facility/{id}.
Annotations the server declares
- title: Get facility
- readOnlyHint: true
metriport_get_medical_record_summaryGet a URL to the Patient's medical record summary rendered as pdf or html.Reads text others writeNo findings
Why it is in this group
- The name "metriport_get_medical_record_summary" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get a URL to the Patient's medical record summary rendered as pdf or html. Medical API: GET /medical/v1/patient/{patientId}/medical-record.
Annotations the server declares
- title: Get medical record summary
- readOnlyHint: true
metriport_get_patientGet a single Patient by its Metriport ID (demographics + facility IDs).No findings
Why it is in this group
- The name "metriport_get_patient" says "get": a word for reading.
Description, as the server wrote it Get a single Patient by its Metriport ID (demographics + facility IDs). Medical API: GET /medical/v1/patient/{id}.
Annotations the server declares
- title: Get patient
- readOnlyHint: true
metriport_list_consolidated_queriesGet the status of the Patient's consolidated-data (FHIR) queries.No findings
Why it is in this group
- The name "metriport_list_consolidated_queries" says "list": a word for reading.
Description, as the server wrote it Get the status of the Patient's consolidated-data (FHIR) queries. Medical API: GET /medical/v1/patient/{id}/consolidated/query.
Annotations the server declares
- title: List consolidated queries
- readOnlyHint: true
metriport_list_documentsList the document references currently available for a Patient at Metriport (optionally filtered by date range and content search).Reads private dataNo findings
Why it is in this group
- The name "metriport_list_documents" says "list": a word for reading.
What it can reach
- private-dataThe name "metriport_list_documents" says "list" and "document": it reads documents.
- private-dataThe description's first sentence says "list" and "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- title: List documents
- readOnlyHint: true
metriport_list_facilitiesList all Facilities under your Metriport Organization (id, name, npi, address).No findings
Why it is in this group
- The name "metriport_list_facilities" says "list": a word for reading.
Description, as the server wrote it List all Facilities under your Metriport Organization (id, name, npi, address). Medical API: GET /medical/v1/facility.
Annotations the server declares
- title: List facilities
- readOnlyHint: true
metriport_list_patientsList Patients — all Patients, or only those at a given Facility if facilityId is supplied.No findings
Why it is in this group
- The name "metriport_list_patients" says "list": a word for reading.
Description, as the server wrote it List Patients — all Patients, or only those at a given Facility if facilityId is supplied. Medical API: GET /medical/v1/patient.
Annotations the server declares
- title: List patients
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://metriport.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://metriport.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://metriport.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://metriport.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.41.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http metriport https://metriport.usefulapi.io/mcpclaude mcp add --transport http metriport https://metriport.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__metriport__metriport_list_facilities",
"mcp__metriport__metriport_get_facility",
"mcp__metriport__metriport_list_patients",
"mcp__metriport__metriport_get_patient",
"mcp__metriport__metriport_list_documents",
"mcp__metriport__metriport_get_document_query_status",
"mcp__metriport__metriport_get_document_url",
"mcp__metriport__metriport_list_consolidated_queries",
"mcp__metriport__metriport_get_medical_record_summary"
],
"ask": [],
"deny": [
"mcp__metriport__metriport_create_patient",
"mcp__metriport__metriport_start_document_query",
"mcp__metriport__metriport_start_consolidated_query"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as metriport. Review it before you use it.
Capability tags behind 4 rules
- mcp__metriport__metriport_list_documents private-data
- mcp__metriport__metriport_get_document_query_status private-data
- mcp__metriport__metriport_get_document_url private-data, untrusted-input
- mcp__metriport__metriport_get_medical_record_summary untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/metriport/verify?hash=d7671af0f0d8e77b7e2a44b30f7a053f70f867fe614423e4ebacca944af1c8e1" | jq -e '.changed == false'Pinned hash d7671af0f0d8, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/metriport/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/metriport)Source: MCP Registry · repository. Synced Nov 21, 2026, 08:17 UTC.
Metriport MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Metriport MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 12 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Metriport MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: metriport_create_patient, metriport_start_document_query and metriport_start_consolidated_query.
Can the Metriport MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Metriport MCP by usefulapi have?
- 12 tools: 3 destructive, 9 read. metriport_create_patient, metriport_start_document_query, metriport_start_consolidated_query, metriport_list_facilities, metriport_get_facility, metriport_list_patients, metriport_get_patient, metriport_list_documents and 4 more.
Does the Metriport MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Metriport MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Metriport MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.