Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@regmd-mcpClassify a wireless pulse oximeter for FDA and EU MDR"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
regmd-mcp
MCP server for regMD — Global Medical Device Regulatory Intelligence.
Classify devices, query regulatory alerts, and find market expansion pathways across 15 jurisdictions — all from your AI assistant.
Install
npx regmd-mcpOr install globally:
npm install -g regmd-mcp
regmd-mcpConfigure
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"regmd": {
"command": "npx",
"args": ["-y", "regmd-mcp"],
"env": {
"REGMD_API_KEY": "your_api_key"
}
}
}
}OpenClaw
Add to your OpenClaw MCP config:
{
"mcpServers": {
"regmd": {
"command": "npx",
"args": ["-y", "regmd-mcp"],
"env": {
"REGMD_API_KEY": "your_api_key"
}
}
}
}Cursor / Windsurf / Any MCP Client
{
"mcpServers": {
"regmd": {
"command": "npx",
"args": ["-y", "regmd-mcp"],
"env": {
"REGMD_API_KEY": "your_api_key"
}
}
}
}Tools
classify_device
Classify a medical device across global regulatory jurisdictions.
Example: "Classify a wireless blood pressure monitor for FDA and EU MDR"
Parameters:
deviceName(required) — Device namedeviceDescription(required) — Description of the deviceintendedPurpose(required) — Clinical intended usetargetMarkets(required) — Array of jurisdiction codes:US,EU,SG,AU,JP,CN,CA,KR,IN,BR,TH,MY,VN,PH,HKdeviceCategory—general,samd,implant,ivd,active,non_active,in_vitrocontactType—non-invasive,invasive-orifice,surgically-invasive,implantable,no-contactdurationOfUse—transient(<60min),short-term(<30 days),long-term(>30 days)isActive— Electrically powered (boolean)hasSoftware— Contains software (boolean)
list_jurisdictions
List all 15 supported regulatory jurisdictions with agency names and details.
get_alerts
Query recent regulatory alerts from FDA, EU-MDCG, and HSA.
Example: "Show me critical FDA alerts from the last 7 days"
Parameters:
jurisdiction—fda,eu-mdr,hsa, orallurgency—critical,plan,awareness, oralllimit— 1-50 (default: 10)days— Last N days (1-90, default: 30)
find_pathway
Find regulatory pathway between jurisdictions.
Example: "What's the pathway from FDA clearance to EU MDR for a Class II device?"
Parameters:
fromJurisdiction(required) — Source jurisdiction codetoJurisdiction(required) — Target jurisdiction codedeviceCategory— Device categoryriskClass— Risk class in source jurisdiction
Coverage
🇺🇸 FDA · 🇪🇺 EU MDR · 🇸🇬 HSA · 🇦🇺 TGA · 🇯🇵 PMDA · 🇨🇳 NMPA · 🇨🇦 Health Canada · 🇰🇷 MFDS · 🇮🇳 CDSCO · 🇧🇷 ANVISA · 🇹🇭 Thai FDA · 🇲🇾 MDA · 🇻🇳 VMOH · 🇵🇭 FDA-PH · 🇭🇰 MDCO
API
The MCP server connects to the regMD REST API at https://regmd.dev/api/v1.
Free: Device classification (basic)
$99 Lifetime Deal: Full access — classification, portfolio, alerts, pathways, timeline, compliance
Get your API key at regmd.dev.
Environment Variables
Variable | Default | Description |
|
| API base URL |
| — | API key for authenticated endpoints |
License
MIT
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.