Use in your browser
Give it a public FHIR base URL and it reads the two documents a server publishes about itself, the /metadata CapabilityStatement and .well-known/smart-configuration, then runs the official HL7 validator over the CapabilityStatement offline. You get SMART discovery state, US Core resource-type coverage, and errors grouped into distinct findings, so one rule broken a hundred times reads as one problem. Coverage is what the server declares, not a compliance score. A run usually takes 20 to 60 seconds.
Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage
Guest access is available after setup. Full account linking verified by PowMCP: Claude only.
Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.
Open the apps workspace
Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.
ClaudeOpen Claude setup Guest access + account linking verified by PowMCP
VS CodeOpen VS Code setup Guest access available · Account linking not yet verified
KiroOpen Kiro setup Guest access available · Account linking not yet verified
LM StudioOpen LM Studio setup Guest access available · Account linking not yet verified
Visual StudioOpen Visual Studio setup (Windows) Guest access available · Account linking not yet verifiedCopy one ready-to-send prompt for any agent that supports remote MCP connections.
For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.
ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide
https://powmcp.com/fhir-server-check/mcp {
"mcpServers": {
"powmcp-fhir-server-check": {
"type": "http",
"url": "https://powmcp.com/fhir-server-check/mcp"
}
}
}Terminal agents add this app with one command:
claude mcp add --transport http powmcp-fhir-server-check https://powmcp.com/fhir-server-check/mcpcodex mcp add powmcp-fhir-server-check --url https://powmcp.com/fhir-server-check/mcpgemini mcp add --transport http powmcp-fhir-server-check https://powmcp.com/fhir-server-check/mcpManage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.
Proof
Read what a public FHIR server declares about itself (its /metadata CapabilityStatement and SMART discovery document) and check it with the official HL7 validator, with US Core resource-type coverage and errors grouped into distinct findings
Fetch a public FHIR R4 server's /metadata CapabilityStatement and its .well-known/smart-configuration without auth, validate the CapabilityStatement structurally with the pinned official HL7 FHIR Validator running offline, and report the resource types and interactions the server declares, US Core server resource-type coverage with a covered/missing split, SMART discovery state and required fields, a combined missing list, and structural errors grouped into distinct findings so a single repeated rule violation is not read as a hundred problems. Every claim is scoped to what the server declares, never to what a live endpoint actually returns.
Request cost1 completed result
Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.
capability_check
Fetches what a public FHIR server publishes about itself (its /metadata CapabilityStatement and, from the same base, its .well-known/smart-configuration) WITHOUT auth, validates the CapabilityStatement structurally with the pinned official HL7 FHIR Validator 6.9.11 running offline, and reads its declarations against US Core server and SMART discovery expectations. Returns a conforms pass/fail, a distinctFindings block that collapses repeated errors into the real number of problems and gives each an occurrence count, a capabilities inventory (declared resources and interactions, US Core server resource-type coverage with a covered/missing split, and SMART discovery state, capabilities, authorization and token endpoints), a combined missing list, raw issue occurrences by severity with source and location, and the validator/package/terminology provenance. Reach for it whenever a public FHIR base URL or /metadata URL is supplied and the question is what that server supports, whether its metadata is valid, why a SMART client cannot discover its endpoints, or simply whether the endpoint is in good shape. It reads DECLARATIONS: US Core coverage here is resource-type presence in the CapabilityStatement, not validation of US Core server requirements such as required searches, _include or Must Support behaviour, and nothing here is evidence that the live endpoint returns conformant data. It inspects one named server and nothing else: it does not validate an individual FHIR resource against a profile, and it does not explain what FHIR or SMART concepts mean, so a question with no server URL in it is not a call for this tool. Offline calls typically take ~15-40 seconds on a large /metadata; tell the user before calling.
Other apps for the jobs next to FHIR Server Check.
Scope and boundaries for FHIR Server Check.
Check the public SMART Health IT R4 base at https://launch.smarthealthit.org/v/r4/fhir, deriving its /metadata and path-relative .well-known/smart-configuration URLs and retaining up to 15 raw validator issues.
Start with conforms and distinctFindings.errorTotal, then fix the first distinct structural error rather than treating repeated occurrences as separate problems. A pass applies only to the published CapabilityStatement; report SMART discovery and US Core resource-type coverage separately, and use live server suites for required searches, Must Support behavior, and endpoint conformance. Missing or unreadable SMART discovery, unchecked terminology, or truncated issues leaves those parts unestablished.
This reads unauthenticated public declarations and validates the CapabilityStatement document offline. Declared US Core coverage is resource-type presence, not proof of required searches, Must Support behavior, SMART conformance, certification, or conformant live data; a server can have structurally valid metadata while its endpoints behave differently.