Health · Remote MCP server
Constat MCP - FDA Device Evidence Lifecycle
FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.healthai/radar- Version
- 0.5.3
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- com.healthai · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain healthai.com · how
- Website
- constat.dev/connect
- Repository
- github.com/healthai-hq/fda-risk-radar
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://constat.dev/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- com.healthai/radar 0.5.3 · protocol 2025-06-18
- Tools discovered
14 - show names
device_risk_lookup,firm_compliance_history,watchlist_diff,device_evidence_lookup,evidence_search,predicate_chain,evidence_cohort_stats,device_postmarket_lookup,postmarket_search,cohort_postmarket_stats,reimbursement_lookup,reimbursement_search,reimbursement_stats,vehicle_risk_lookup- Checked on
- 2026-10-05
How to connect Constat MCP - FDA Device Evidence Lifecycle
Constat MCP - FDA Device Evidence Lifecycle is a remote MCP server: there is nothing to install. Its endpoint is https://constat.dev/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.healthai
| Server | Runs |
|---|---|
| Clarity by Health AICondition-aware ingredient and product checks for agents, with evidence tiers and citations. | Remote · HTTPLive check: ✓ handshake |
More health servers
| Server | Runs |
|---|---|
| CMS Medicare DataMedicare spending, chronic conditions, hospital quality, readmissions, and enrollment. | Remote · HTTPLive check: ✓ handshake |
| Coach MCPYour endurance training data in your AI assistant: activities, recovery, plan, workout edits. | Remote · HTTPLive check: sign-in required |
| Coach WattsRemote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0. | Remote · HTTPLive check: sign-in required |
| Cochrane Medical ReviewsSystematic medical reviews and evidence-based healthcare research. | Remote · HTTPLive check: ✓ handshake |
| Convergent Provider DirectorySearch a healthcare provider directory and get full provider details by id. | Remote · HTTPLive check: ✓ handshake |
| Costkits MCPMCP server for CostKits: live healthcare procedure cost estimates and provider pricing. | Local · stdio |
| CounterScript - Drug Price BenchmarksFree US drug-price benchmarks from federal data (CMS NADAC): a benchmark, not a price anyone owes. | Remote · HTTPLive check: ✓ handshake |
| Coverage ExceptionWhy Medicare Part D restricts a drug, and the exception and appeal path to challenge it. | Remote · HTTPLive check: ✓ handshake |