Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Constat MCP — FDA Device Evidence Lifecycle

REMOTE · CONSTAT.DEV

FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance.

Available components

0 this week 23 Trust /100

Last scanned (8 hours ago)

Scores higher than 8% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 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
  • 26 Aug 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
  • 11 Aug 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
  • 9 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.43 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 2 Aug 26 0
    • HTTPS: unverified → pass ▲ security
  • 1 Aug 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
  • 31 Jul 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
Diagnostics

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 5 Nov 2026 · Probed https://constat.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=constat.dev CN=WE1,O=Google Trust Services,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA256 e08d05a79723d79413561d50dab0afe2
SANs: constat.dev, www.constat.dev, *.www.constat.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of constat.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
constat.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 400

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://constat.dev/api/mcp HTTP error 400
http (plaintext) http://constat.dev/api/mcp HTTPS enforced 301 https://constat.dev/api/mcp
MCP tools · 14 exposed · ~1,916 tokens

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 →

Tool Tokens
cohort_postmarket_stats ~89

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 denominator inline, never pooled across devices.

NameTypeReqDescription
panelstring–Advisory panel, e.g. Radiology; omit for all
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

device_evidence_lookup ~110

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 chain, PCCP — each with a verbatim source quote and page. Null means the summary did not state it.

NameTypeReqDescription
k_numberstringyes510(k) or De Novo number, e.g. K252148 or DEN180001
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

device_postmarket_lookup ~123

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). Descriptive observables with sources — never a safety judgment.

NameTypeReqDescription
k_numberstringyes510(k) or De Novo number, e.g. K252148 or DEN180001
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

device_risk_lookup ~87

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 interpretation limits. It does not predict enforcement against a firm.

NameTypeReqDescription
product_codestringyesFDA product code, e.g. FRN
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

evidence_cohort_stats ~121

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 every denominator and discloses the parse queue separately. Predicate age (median years between a clearance and its cited predicates) is included when decision-date coverage clears a 60% floor, and withheld otherwise.

NameTypeReqDescription
panelstring–Advisory panel, e.g. Radiology; omit for all
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

evidence_search ~210

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 matching records with their parsed evidence. Presence flags are descriptive: 'reports a sensitivity metric' is not 'reports a comparable sensitivity' — analysis units differ across devices.

NameTypeReqDescription
applicantstring–Substring match on applicant/company name
has_clinical_databoolean––
has_pccpboolean–Included a Predetermined Change Control Plan
limitinteger––
panelstring–Advisory panel, e.g. Radiology
product_codestring–FDA product code, e.g. QAS
reports_any_sensitivity_metricboolean–Reported any sensitivity metric (canonical — includes per-finding sensitivities, not just the top-level slot). Not a claim of cross-device comparability.
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

firm_compliance_history ~200

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 or may be supplied explicitly. Returns attribution and coverage limits with the records; it is not a finding of noncompliance or a prediction of FDA action.

NameTypeReqDescription
fei_numbersarray–Optional exact FDA FEI numbers; improves Form 483 attribution.
firm_namestringyesFDA applicant or company name, e.g. 'Medtronic'
limitinteger–Maximum records per source and events in the timeline (default 50).
product_codesarray–Optional FDA product-code scope. When omitted, Constat discovers codes from applicant matches in its device corpus.
sincestring–Earliest event date, YYYY-MM-DD. Defaults to five years ago.
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

postmarket_search ~225

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.

NameTypeReqDescription
applicantstring–Substring match on applicant/company name
has_drift_signalboolean––
limitinteger––
maude_trend_upboolean–Code-level MAUDE trend above its own 3-year baseline
min_recalls_24mointeger–Product-code recalls in trailing 24 months
panelstring–Advisory panel, e.g. Radiology
product_codestring–FDA product code, e.g. QIH
signal_specificitystring–Restrict the drift-signal filter to one tier: 'device' = attributable to this device (own line re-cleared, own applicant's recall, predicate neighbors) — the high-signal tier; 'product_code' = observ…
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

predicate_chain ~92

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.

NameTypeReqDescription
depthinteger–Max ancestry depth (default 4)
k_numberstringyes510(k) or De Novo number, e.g. K252148 or DEN180001
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

reimbursement_lookup ~184

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 amounts, effective dates, and source links, plus any commercial/MAC payer coverage policies that reference the clearance or its codes. Answers 'who got paid, how much, through which mechanism, on what basis.' CPT codes are bare factual identifiers only — no procedure descriptors; follow the CMS source link for the official descriptor.

NameTypeReqDescription
cpt_codestring–Bare CPT code, e.g. 75580 or 0932T
k_numberstring–FDA clearance number, e.g. DEN170073 or K252148
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

reimbursement_search ~157

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 with amounts, effective dates, and sources. Use reimbursement_stats for the mechanism distribution (never a single pooled reimbursement rate).

NameTypeReqDescription
applicantstring–Substring match on device maker / applicant name
cpt_categorystring–CPT category
has_cms_rateboolean–Only pathways with a known CMS dollar rate
limitinteger––
mechanismstring–Payment mechanism
ntap_statusstring––
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

reimbursement_stats ~84

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 'reimbursement rate': NTAP add-on amounts and CMS rates are different measurements and are reported separately with their own spreads.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

vehicle_risk_lookup ~85

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).

NameTypeReqDescription
makestringyese.g. honda
modelstringyese.g. civic
yearstringyesmodel year, e.g. 2020
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

watchlist_diff ~149

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 the last seven days. Analyst verdict text and internal review status are excluded; use next_since as the next polling cursor.

NameTypeReqDescription
limitinteger–Maximum changes to return (default 100).
product_codesarray–FDA product codes to poll. Omit for the default Radar watchlist.
sincestring–Return changes on or after this ISO date or UTC timestamp. Defaults to the last seven days; pass the prior response's next_since for exact polling.
NameTypeReqDescription
data–yes–
messagestring––
statusstringyes–

No examples provided.

Install

How do I install the Constat MCP — FDA Device Evidence Lifecycle server?

Constat MCP — FDA Device Evidence Lifecycle is a hosted endpoint at https://constat.dev/api/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 · constat.dev

# add to Claude Code
claude mcp add --transport http com-healthai-radar 'https://constat.dev/api/mcp'
Common questions

What is the Constat MCP — FDA Device Evidence Lifecycle server?

Constat MCP — FDA Device Evidence Lifecycle is listed in the public MCP registry as com.healthai/radar. FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance. This page covers its hosted endpoint (https://constat.dev/api/mcp).

Is the Constat MCP — FDA Device Evidence Lifecycle server safe to use?

Constat MCP — FDA Device Evidence Lifecycle scores 23 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 Constat MCP — FDA Device Evidence Lifecycle server expose?

Constat MCP — FDA Device Evidence Lifecycle exposes 14 tools: device_risk_lookup, firm_compliance_history, watchlist_diff, device_evidence_lookup, evidence_search, and 9 more. Their descriptions and schemas cost roughly 1,916 tokens of context every time the server is loaded.

Does the Constat MCP — FDA Device Evidence Lifecycle server require authentication?

Its publisher declares no required credentials for Constat MCP — FDA Device Evidence Lifecycle. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Constat MCP — FDA Device Evidence Lifecycle server still maintained?

Constat MCP — FDA Device Evidence Lifecycle is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.