Constat MCP — FDA Device Evidence Lifecycle

com.healthaiPublished by healthai.comv0.5.3Updated Oct 24, 2026

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

The publisher's own server: Clarity by Health AI

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant FDA and CMS evidence on AI medical devices, covering 510(k) clearances, postmarket data, reimbursement and device-

What you can do
Look up FDA and CMS evidence for AI medical devices, including 510(k) clearance records, postmarket information, reimbursement details and compliance material. No individual tools are listed, so the exact operations available are not documented in the supplied material.
When to use it
Useful when you need regulatory, reimbursement or postmarket context on AI medical devices and want an assistant to pull that evidence rather than search manually.
Requirements
A remote streamable HTTP endpoint at constat.dev; no packages, environment variables or headers are declared. The manifest declares no authentication, but access conditions are not otherwise documented.
Before you install
The manifest declares no authentication and no credentials, and no tool list or README is provided, so what data is sent to the remote service and what actions it can take cannot be verified before connecting. Treat regulatory and reimbursement findings as evidence to check, not as authoritative advice.

Installation

In SourceWeft

  1. Open Constat MCP — FDA Device Evidence Lifecycle in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.healthai%2Fradar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "constat-fda-device-evidence-lifecycle": {
      "type": "http",
      "url": "https://constat.dev/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.5.3LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Healthai integrations

Clarity by Health AI

com.healthaiOfficial publisher

Lets an assistant check ingredients and products against a person's health conditions, returning evidence tiers and citations.

Streamable HTTPWeb executable
Location & LifestyleNot indexed yetOct 24, 2026