Constat MCP — FDA Device Evidence Lifecycle

Official registry Health

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http constat-mcp-fda-device-evidence-lifecycl 'https://constat.dev/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "constat-mcp-fda-device-evidence-lifecycl": {
            "type": "http",
            "url": "https://constat.dev/api/mcp"
        }
    }
}

Frequently asked questions

What is Constat MCP — FDA Device Evidence Lifecycle?

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

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

It runs as a remote server. In Claude Code: claude mcp add --transport http constat-mcp-fda-device-evidence-lifecycl 'https://constat.dev/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Constat MCP — FDA Device Evidence Lifecycle need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Constat MCP — FDA Device Evidence Lifecycle open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Constat MCP — FDA Device Evidence Lifecycle?

It is published by healthai-hq. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.