Koskamo

MedicalClaim.ai MCP

A pre-submission claims intelligence platform providing denial risk analysis, NCCI bundling conflict detection, MUE limit lookup, DRG weight reference, and payer-specific reimbursement data for Medicare. It allows agents to look up CMS Local Coverage Articles, ICD-10 diagnosis coverage, and Physician Fee Schedule rates for CPT/HCPCS codes.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

MedicalClaim.ai MCP logo, by BuiltForAI, LLCCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by BuiltForAI, LLC
MCP endpoint (Streamable HTTP)
https://medicalclaim.ai/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (1)

1 of 1 have a description · 0 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check Medicare coverage status for specific procedure codes against a diagnosis
  • Retrieve CMS Physician Fee Schedule payment rates for professional and facility settings
  • Detect NCCI bundling conflicts and MUE limits for claim validation
  • Decode CARC denial codes and reference DRG weights for inpatient groups

Source and maintenance

Community listingRegistry 1.0.0
mcp-registry: io.github.builtforai/procedure-coverage@1.0.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
builtforai-medicalclaim 1.0.0
MCP protocol negotiated in check
2024-11-05
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

1 advertised

medicare_procedure_coverage
Advertised by the server during the last successful anonymous check.

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.

medicare_procedure_coverage input schema
{
  "type": "object",
  "required": [],
  "properties": {
    "codes": {
      "type": "string",
      "description": "Comma-separated CPT/HCPCS codes, e.g. \"27447,20610\""
    },
    "diagnosis": {
      "type": "string",
      "description": "ICD-10 code or prefix, e.g. \"M17\" (knee osteoarthritis)"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
260 ms
95th percentile latency
260 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 260 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http medicalclaim-ai-mcp https://medicalclaim.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add medicalclaim-ai-mcp --url https://medicalclaim.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable medicalclaim-ai-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "medicalclaim-ai-mcp": {
      "url": "https://medicalclaim.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "medicalclaim-ai-mcp": {
      "type": "streamableHttp",
      "url": "https://medicalclaim.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start medicalclaim-ai-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "medicalclaim-ai-mcp": {
      "type": "http",
      "url": "https://medicalclaim.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http medicalclaim-ai-mcp https://medicalclaim.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://medicalclaim.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "medicalclaim-ai-mcp": {
      "serverUrl": "https://medicalclaim.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like MedicalClaim.ai MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 7,068