Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.builtforai/procedure-coverage

REMOTE · MEDICALCLAIM.AI

Medicare coverage and fee-schedule amounts for CPT/HCPCS codes against a diagnosis

Available components

0 this week 76 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 227 tokens (~227/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
  • 10 Oct 26 0
    • HTTPS: unverified → pass ▲ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://medicalclaim.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=medicalclaim.ai CN=YE1,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 5cba6df3e0e98ec0d99b08884b18b11783e
SANs: *.medicalclaim.ai, medicalclaim.ai
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of medicalclaim.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
medicalclaim.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://medicalclaim.ai/mcp Verified 200
http (plaintext) http://medicalclaim.ai/mcp HTTPS enforced 301 https://medicalclaim.ai/mcp
MCP tools · 1 exposed · ~227 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
medicare_procedure_coverage ~227

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

NameTypeReqDescription
codesstring–Comma-separated CPT/HCPCS codes, e.g. "27447,20610"
diagnosisstring–ICD-10 code or prefix, e.g. "M17" (knee osteoarthritis)

No output schema declared.

No examples provided.

Install

How do I install the io.github.builtforai/procedure-coverage MCP server?

io.github.builtforai/procedure-coverage is a hosted endpoint at https://medicalclaim.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · medicalclaim.ai

# add to Claude Code
claude mcp add --transport http builtforai-procedure-coverage 'https://medicalclaim.ai/mcp'
Common questions

What is the io.github.builtforai/procedure-coverage MCP server?

io.github.builtforai/procedure-coverage is an MCP server listed in the public MCP registry as io.github.builtforai/procedure-coverage. Medicare coverage and fee-schedule amounts for CPT/HCPCS codes against a diagnosis. This page covers its hosted endpoint (https://medicalclaim.ai/mcp).

Is the io.github.builtforai/procedure-coverage MCP server safe to use?

io.github.builtforai/procedure-coverage scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.builtforai/procedure-coverage MCP server expose?

io.github.builtforai/procedure-coverage exposes 1 tool: medicare_procedure_coverage. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

Does the io.github.builtforai/procedure-coverage MCP server require authentication?

No. We connected to io.github.builtforai/procedure-coverage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.builtforai/procedure-coverage MCP server still maintained?

io.github.builtforai/procedure-coverage is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.builtforai/procedure-coverage MCP server?

VerifyMCP ran 12 checks on io.github.builtforai/procedure-coverage, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.builtforai/procedure-coverage: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.