io.github.builtforai/procedure-coverage
REMOTE · MEDICALCLAIM.AI · SCANNED SEP 29
Medicare coverage and fee-schedule amounts for CPT/HCPCS codes against a diagnosis
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http builtforai-procedure-coverage 'https://medicalclaim.ai/mcp'
{
"mcpServers": {
"builtforai-procedure-coverage": {
"url": "https://medicalclaim.ai/mcp"
}
}
} {
"servers": {
"builtforai-procedure-coverage": {
"type": "http",
"url": "https://medicalclaim.ai/mcp"
}
}
} [mcp_servers.builtforai-procedure-coverage] url = "https://medicalclaim.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"builtforai-procedure-coverage": {
"type": "remote",
"url": "https://medicalclaim.ai/mcp",
"enabled": true
}
}
} openclaw mcp add builtforai-procedure-coverage --url 'https://medicalclaim.ai/mcp' --transport streamable-http
mcp_servers:
builtforai-procedure-coverage:
url: "https://medicalclaim.ai/mcp" {
"McpServers": {
"builtforai-procedure-coverage": {
"Transport": "http",
"Url": "https://medicalclaim.ai/mcp"
}
}
} assistant mcp add builtforai-procedure-coverage -t streamable-http -u 'https://medicalclaim.ai/mcp'
{
"mcpServers": {
"builtforai-procedure-coverage": {
"type": "http",
"url": "https://medicalclaim.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 58
First indexed and scored.
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 29 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 50d77970618c656dd8a48418c4287d834b2 |
| 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. | present | 3799 | 8 | Verified |
| medicalclaim.ai. | absent | 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 | Inconclusive | 301 | http://medicalclaim.ai/mcp/ |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | string | – | Comma-separated CPT/HCPCS codes, e.g. "27447,20610" |
| diagnosis | string | – | ICD-10 code or prefix, e.g. "M17" (knee osteoarthritis) |
No output schema declared.
No examples provided.
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 63 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 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.