@openquality/mcp

MCPattestedlive
v0.2.0UnknownMITUpdated 5d agonpmGitHub

Read-only MCP server for the Open Quality measure corpus: measure code, provenance, known issues and CRMI Bundles

Endpoint healthlive
checked 1 day ago · 373ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
454Downloads/wk
1GitHub stars
1Forks
5d agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.2.0
Sourcenpm+mcp-registry
npm@openquality/mcp
GitHubFHIR-IQ/openquality
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · dd605bb
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.2.0 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 16, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev0.2.0 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

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

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Read-only MCP server for the Open Quality measure corpus: measure code, provenance, known issues and CRMI Bundles

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-17 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

56 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+44 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.