Fhirlint vs PayMCP
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
Validate FHIR R4/R5 resources and bundles against profiles (US Core, etc.) with precise, line-level error reporting.
Comparison
| Feature | Fhirlint | PayMCP |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | 2 |
| Rating | — | — |
| Verified | — | |
| Hosted | — | — |
| Tools | — | — |
| Category | development | development |
| Author | cognis-digital | blustAI |
| Repo | cognis-digital/fhirlint | blustAI/paymcp |
When to pick Fhirlint
Validate FHIR R4/R5 resources and bundles against profiles (US Core, etc.) with precise, line-level error reporting.
When to pick PayMCP
Lightweight payments layer for MCP servers: turn tools into paid endpoints with a two-line decorator. [PyPI](https://pypi.org/project/paymcp/) · [npm](https://www.npmjs.com/package/paymcp) · [TS repo](https://github.com/blustAI/paymcp-ts)
Looking for something else? Browse all MCPs or check trending this week.