
Uscore Profile Gap Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.1Updated Oct 27, 2026
Finds the FHIR R4 resources still pinned to US Core 3.1.1 or 5.0.1, and the USCDI v3 Patient element
Overview
A local stdio MCP server that finds FHIR R4 resources still pinned to US Core 3.1.1 or 5.0.1 and the USCDI v3 Patient element.
- What you can do
- Scan FHIR R4 resources for version-pinned US Core profiles (3.1.1 and 5.0.1).
- Identify the USCDI v3 Patient element in those resources.
- Report the gaps found so they can be reviewed or fixed.
- No individual tools are listed in the manifest, so the exact operations are not documented.
- When to use it
- Useful when auditing or upgrading a FHIR R4 implementation guide to newer US Core versions and you want an assistant to point out resources still on 3.1.1 or 5.0.1 and missing the USCDI v3 Patient element.
- Requirements
- Runs as a local process via npx from the npm package @readystack/uscore-profile-gap-lint; Node.js is needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Installation
In SourceWeft
- Open Uscore Profile Gap Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.1LatestSep 19, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.