Constat MCP — FDA Device Evidence Lifecycle
FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance
Reviews
No review yet. Used Constat MCP — FDA Device Evidence Lifecycle? Be the first to help others choose.What it does
Constat MCP — FDA Device Evidence Lifecycle is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 12h ago (live check)Hosted endpoint
https://constat.dev/api/mcpstreamable-http
In Claude Code: claude mcp add --transport http constat-mcp-fda-device-evidence-lifecycle https://constat.dev/api/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"constat-mcp-fda-device-evidence-lifecycle": {
"url": "https://constat.dev/api/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 12h agoONLINE Constat MCP — FDA Device Evidence Lifecycle answered an MCP connection on 17 Nov 2026 and introduced itself as com.healthai/radar 0.5.3 (MCP protocol 2025-06-18).
14 tools offered to AI assistants
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 normalized category signal, its driver contributions, and ifirm_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 codes are discovered from Constat's AI/ML-device corpus orwatchlist_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. Defaults to Constat Radar's five-code watchlist and thedevice_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, sample sizes, endpoints, reported performance, predicate chevidence_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 evidence did FDA accept for devices like mine'. Returns bounded dispredicate_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 older predicates.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 pooled performance value. Excludes not-yet-parsed devices from edevice_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, rpostmarket_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-device postmarket summaries with drift-signal counts.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, with a warning-letter match — every rate with its denominatorreimbursement_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-on, Category I/III CPT + CMS rate, HCPCS, MAC LCD) with amoureimbursement_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: mechanism, CPT category, NTAP status, applicant. Returns pathways
Show 2 more
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. Deliberately never a single pooled 'rvehicle_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).
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://constat.dev/api/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://constat.dev/connect | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/healthai-hq/fda-risk-radar | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 0.5.3 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Constat MCP — FDA Device Evidence Lifecycle still online?
Free alerts · no account▲ 0Do you run Constat MCP — FDA Device Evidence Lifecycle? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Constat MCP — FDA Device Evidence Lifecycle
How do I connect Constat MCP — FDA Device Evidence Lifecycle?
Use the hosted endpoint https://constat.dev/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Constat MCP — FDA Device Evidence Lifecycle offer?
When Electra Index connected on 17 Nov 2026, it listed 14 tools: device_risk_lookup, firm_compliance_history, watchlist_diff, device_evidence_lookup, evidence_search, predicate_chain, evidence_cohort_stats, device_postmarket_lookup and more. The full list is in "Live check" above.
Is Constat MCP — FDA Device Evidence Lifecycle online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 12h ago.