procedure-coverage
io.github.builtforai/procedure-coverageVersion 1.0.0Medicare coverage and fee-schedule amounts for CPT/HCPCS codes against a diagnosis
Status
Responds169 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:46 UTC
- Latency
- 169 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://medicalclaim.ai/mcpResponds169 msNo sign-in
Claude Code
claude mcp add --transport http procedure-coverage https://medicalclaim.ai/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: procedure-coverage
Remote MCP server URL: https://medicalclaim.ai/mcpCursor
{
"mcpServers": {
"procedure-coverage": {
"url": "https://medicalclaim.ai/mcp"
}
}
}VS Code
code --add-mcp '{"name":"procedure-coverage","type":"http","url":"https://medicalclaim.ai/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
1 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
medicare_procedure_coverageFor a diagnosis and one or more CPT/HCPCS codes, report what CMS Local Coverage Articles record for each code, which ICD-10 diagnoses those articles list as covered or non-covered, and the CMS Physician Fee Schedule PROFESSIONAL amount where a national rate exists. Setting matters and is stated: codes performed only in a facility return not_applicable_in_this_setting rather than an invented office price, and codes CMS does not pay under the PFS (status I, X, N, E, B, P) return not_payable_under_pfs rather than a figure computed from published RVUs. Coverage is contractor-specific. Does NOT compare clinical effectiveness or recommend treatment, and a missing national rate is never treated as non-coverage. The amount is the clinician fee only — not the facility fee, device or imaging. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Categories
- Uncategorized
- GDPR
- Not declared