INDIVIDUAL MCP TOOL

reimbursement_stats

Distribution of payment mechanisms across the AI/ML reimbursement corpus — pathway and distinct-device counts per mechanism (NTAP, Cat I, Cat III/APC, …) with the min/median/max dollar amounts for each.

constat.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://constat.dev/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for reimbursement_stats and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description suggests a financial action.

Parent server

constat.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.com-healthai-radar]
url = "https://constat.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "com-healthai-radar": {
      "type": "http",
      "url": "https://constat.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: com-healthai-radar
Remote MCP URL: https://constat.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "com-healthai-radar": {
      "url": "https://constat.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "com-healthai-radar": {
      "type": "http",
      "url": "https://constat.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "com-healthai-radar",
  "transport": "streamable-http",
  "url": "https://constat.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

device_risk_lookup — Review a medical-device category's public FDA signals by three-letter product code (e.g.
firm_compliance_history — Build a recent, source-bounded FDA public-record timeline for a device firm: matched recalls, warning letters, and Form 483 citations where exact FEI numbers are available.
watchlist_diff — Return machine-generated FDA public-record changes detected for monitored product codes since a caller-supplied date, plus each code's latest category snapshot and postmarket coverage.
device_evidence_lookup — Look up the structured premarket evidence FDA accepted for a specific AI/ML-enabled device by 510(k) number (e.g.
evidence_search — Find AI/ML device clearances by filter — product code, panel, applicant, and whether the submission reported clinical data, any sensitivity metric, or a PCCP.
predicate_chain — Trace the predicate ancestry of a 510(k) device, with each cited predicate's age (how many years old the predicate was when the child cleared).
evidence_cohort_stats — Reporting-rate stats across the parsed AI/ML corpus (optionally by panel).
device_postmarket_lookup — Post-clearance intelligence for one AI/ML device by 510(k) number: its product code's recalls, MAUDE adverse-event level and trend, warning-letter and 483 matches for the applicant, plus per-device drift signals (adverse-event inflection, re-clearances of the same device line, software-recall patterns, predicate-cohort recall activity).