Constat — 483 Risk Radar
Constat — 483 Risk Radar (MCP server)
The MCP server behind Constat — FDA & NHTSA regulatory-risk intelligence for AI agents, over the Model Context Protocol. Live public regulatory data — recalls, adverse events, warning letters, 510(k) premarket evidence, postmarket drift signals, reimbursement pathways, and vehicle safety. Decision support, not regulatory advice.
Endpoint:
https://constat.dev/api/mcp(legacyhttps://radar.healthai.com/api/mcpstill serves)Transport: Streamable HTTP (JSON-RPC 2.0)
Auth: none for the free tier (60 req/min per IP; an optional
X-API-Keyheader raises limits — shared with Clarity MCP, request one atPOST https://mcp.healthai.com/register)Registry:
com.healthai/radar(official MCP registry)
The evidence corpus and tool logic run hosted at the endpoint above. This repo
also ships server.mjs, a zero-dependency stdio bridge to that endpoint, so
stdio-only MCP clients can use the server like any local one:
node server.mjs # stdio MCP server, bridges to constat.dev/api/mcp// e.g. in an MCP client config
{ "mcpServers": { "constat": { "command": "node", "args": ["/path/to/server.mjs"] } } }docker build -t constat-mcp . && docker run -i constat-mcp # same, containerizedTools
Tool | What it does |
| FDA compliance risk for a device category by 3-letter product code — recalls, MAUDE trend, warning-letter matches, composite score |
| Source-bounded FDA public-record timeline for a device firm — recalls, warning letters, 483s, clearances |
| Machine-detected FDA public-record changes for monitored product codes since a given date |
| Parsed 510(k) premarket evidence for an AI/ML device, each field with a verbatim source quote + page |
| Find AI/ML clearances by product code, panel, applicant, clinical data, sensitivity metric, or PCCP |
| Trace a device's predicate ancestry with each predicate's age at clearance |
| Reporting-rate stats across the parsed AI/ML corpus — presence figures with denominators |
| Post-clearance intelligence for one device — recalls, MAUDE trend, letter/483 matches, drift signals |
| Find devices by postmarket criteria — drift signals, recalls in 24mo, rising MAUDE trend |
| Postmarket presence rates across the AI/ML cohort, each with its denominator |
| Clearance-to-payment pathway by K/DEN or CPT code — NTAP, Cat I/III, CMS rates, HCPCS, LCDs |
| Find payment pathways by mechanism, CPT category, NTAP status, applicant |
| Mechanism distribution across the reimbursement corpus with dollar ranges |
| NHTSA safety history by make/model/year — recall campaigns and complaint stats |
Related MCP server: Legal Info MCP Server
Quick start
curl -s https://constat.dev/api/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"device_risk_lookup","arguments":{"product_code":"FRN"}}}'List tools with {"method":"tools/list"}. Note the Accept header must include
text/event-stream (streamable-HTTP requirement).
Related servers
Clarity MCP — condition-aware ingredient, product & supplement safety (verdict + evidence tier + citation).
MCP Queen — the graded MCP registry that independently probes and grades this server.
About
Built by Health AI, the team behind Constat. Informational only; verify against primary FDA/NHTSA sources.
License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/thehealthai/fda-risk-radar-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server