Regmd MCP Server

MCP server for regMD — Medical Device Regulatory Intelligence. Classify devices, query alerts, find pathways across 15 jurisdictions.

Local serverstdio

What is the Regmd MCP MCP server?

Regmd MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Regmd MCP directly instead of describing what you should do. MCP server for regMD — Medical Device Regulatory Intelligence. Classify devices, query alerts, find pathways across 15 jurisdictions.

Setting it up

The server ships on npm as regmd-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Regmd MCP is connected, these are the calls the assistant has available:

  • Free — ** Device classification (basic)
  • OpenClaw — The OpenClaw tool exposed by this server
  • classify_device — Classify a medical device across global regulatory jurisdictions
  • list_jurisdictions — List all 15 supported regulatory jurisdictions with agency names and details
  • get_alerts — The get_alerts tool exposed by this server
  • find_pathway — The find_pathway tool exposed by this server

Configuration and credentials

You will need 2 environment variables: REGMD_API_KEY, REGMD_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the regmd mcp mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Regmd MCP's toolset — Free, OpenClaw, classify_device and 3 more — is a fair guide to whether it matches your workflow. It is maintained by zubi-wiz; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Regmd MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Free** Device classification (basic)
OpenClawThe OpenClaw tool exposed by this server.
classify_deviceClassify a medical device across global regulatory jurisdictions.
list_jurisdictionsList all 15 supported regulatory jurisdictions with agency names and details.
get_alertsThe get_alerts tool exposed by this server.
find_pathwayThe find_pathway tool exposed by this server.

How to install the Regmd MCP MCP server

{
  "mcpServers": {
    "regmd": {
      "command": "npx",
      "args": ["-y", "regmd-mcp"],
      "env": {
        "REGMD_API_KEY": "your_api_key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
REGMD_API_KEYCredential the server authenticates with.Yes
REGMD_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Regmd MCP to Free.
  • Use Regmd MCP to OpenClaw.
  • Use Regmd MCP to classify device.

Frequently asked questions

It connects Regmd MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Free, OpenClaw, classify_device, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Regmd MCP directly.