MCP servercom.healthai/radar
FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance.
Overview
Score?
UNRATED 0.681
of what a free look can see, on 32 looks
Looks
36
last 2 hr ago
Tools
14
More info
URL
constat.dev/api/mcp
streamable-http
Says it is
com.healthai/radar 0.5.3
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.681 · highest on record 0.8561
Toolsfrom sha256:cc0f16e250…a64f7e
| Tool | Schema |
|---|---|
| cohort_postmarket_stats Postmarket presence rates across the snapshotted AI/ML device cohort (optionally by panel): share with any recall in 24 months, with a rising MAUDE trend, with any drift signal, wi |
input · output |
| device_evidence_lookup Look up the structured premarket evidence FDA accepted for a specific AI/ML-enabled device by 510(k) number (e.g. K252148). Returns parsed summary fields — validation study design, |
input · output |
| 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 |
input · output |
| device_risk_lookup Review a medical-device category's public FDA signals by three-letter product code (e.g. FRN = infusion pump). Returns recalls, MAUDE adverse-event trend, warning-letter matches, a |
input · output |
| evidence_cohort_stats Reporting-rate stats across the parsed AI/ML corpus (optionally by panel). Each rate is a presence figure with its denominator — 'reported in X of Y audited devices' — never a pool |
input · output |
| 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. Answers 'what evidenc |
input · output |
| 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. Product |
input · output |
| postmarket_search Find AI/ML devices by postmarket criteria — product code, panel, applicant, whether any drift signal exists, minimum recalls in 24 months, or a rising MAUDE trend. Returns per-devi |
input · output |
| 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). Reveals how AI/ML devices chain to o |
input · output |
| reimbursement_lookup Trace the clearance-to-payment pathway for an AI/ML device by FDA clearance number (K/DEN, e.g. DEN170073) OR bare CPT code (e.g. 75580). Returns every payment mechanism (NTAP add- |
input · output |
| reimbursement_search Find AI/ML device payment pathways by mechanism — e.g. 'devices that got NTAP', 'devices paid under a Category I CPT code', 'pathways with a known CMS dollar rate'. Filters: mechan |
input · output |
| 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 do |
input · output |
| vehicle_risk_lookup Look up NHTSA safety history for a vehicle by make, model, and model year. Returns recall campaigns and complaint statistics (crashes, fires, injuries, top components). |
input · output |
| 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 cover |
input · output |
Verify it yourself
npx teppi-check https://constat.dev/api/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ26TT043TEJMYRZ946432