Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Open Quality

NPM · @OPENQUALITY/MCP · 2 COMPONENTS

Open healthcare quality measures: CQL, SQL and FHIR with provenance and known issues

+4 this week 85 Trust /100

Last scanned (21 hours ago)

Scores higher than 87% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.31.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to FHIR-IQ/openquality). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 22 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 546 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 23 Oct 26 +4
    • Stability: unverified → 0.27 ▲ functional
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 4 Nov 2026 · Analysed npm/@openquality/mcp@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo FHIR-IQ/openquality
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/FHIR-IQ/openquality/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.2.0
Rekor log index 3235886706
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9b557b29bf1da71ee91b435003f5b6ef087054686b23ba2a9b5e42503b5b9ca924751184952432384b0d7e67545d9e71a740dc570fa2aa3af51ae1e32

Background: How many MCP packages publish verified provenance →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 94 packages
Packages resolved 94
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~447 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. 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 →

Tool Tokens
get_artifact ~49

The raw text of one file a package lists: CQL, SQL, a ViewDefinition, or a FHIR Measure.

NameTypeReqDescription
pathstringyesA path from get_measure `artifacts`

No output schema declared.

No examples provided.

get_bundle ~73

The package as a CRMI artifact Bundle, the shape CRMI's $package returns: an asset-collection Library, then the Measure, its Library and every shared library it depends on.

NameTypeReqDescription
idstringyesPackage id, for example cms/diabetes-glycemic-status-assessment-greater-than-9

No output schema declared.

No examples provided.

get_measure ~71

A package: title, steward, license, provenance (upstream commit, unmodified or derived, and exactly what changed), value set references, file list and known issue summaries.

NameTypeReqDescription
idstringyesPackage id, for example cms/diabetes-glycemic-status-assessment-greater-than-9

No output schema declared.

No examples provided.

known_issues ~102

Interpretation issues, defects, test cases and implementation notes, with their full text. Read these before writing or reviewing measure logic.

NameTypeReqDescription
limitinteger–Maximum results, default 20
measurestring–Package id, for example cms/diabetes-glycemic-status-assessment-greater-than-9
statusstring–open or resolved
typestring–interpretation-issue, defect, test-case or implementation-note

No output schema declared.

No examples provided.

search_measures ~152

Find measure packages by CMS id, title words, steward or package id. Every word must match. Shared CQL libraries are packages too; pass kind "library" to search them.

NameTypeReqDescription
collectionstring–Limit to a collection, for example cms-fhir-2026 or community
dataModelstring–Limit to a data model, for example qi-core or sql-on-fhir
kindstring–measure (default), library for shared CQL libraries such as FHIRHelpers, or any
limitinteger–Maximum results, default 20
querystringyesWords to match, for example "CMS122" or "diabetes glycemic"

No output schema declared.

No examples provided.

Install

How do I install the Open Quality MCP server?

Open Quality runs locally as an npm package, launched with npx -y @openquality/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @openquality/mcp

# add to Claude Code
claude mcp add us-openquality-mcp -- npx -y @openquality/mcp
Common questions

What is the Open Quality MCP server?

Open Quality is an MCP server listed in the public MCP registry as us.openquality/mcp. Open healthcare quality measures: CQL, SQL and FHIR with provenance and known issues. This page covers its npm package (@openquality/mcp).

Is the Open Quality MCP server safe to use?

Open Quality scores 85 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Open Quality MCP server expose?

Open Quality exposes 5 tools: search_measures, get_measure, get_artifact, get_bundle, known_issues. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.

Is the Open Quality MCP server still maintained?

Open Quality is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Open Quality MCP server under?

Open Quality declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.