AgentArmorHQ
Sign in

Constat MCP — FDA Device Evidence Lifecycle

MCP server · GitHub · graded 2026-10-23Source linked

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

No outside reports on file

Constat MCP — FDA Device Evidence Lifecycle is distributed via GitHub (healthai-hq/fda-risk-radar); review its source code, dependencies, and requested permissions before use.

Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Constat MCP — FDA Device Evidence Lifecycle helpful?

What it can access

  • Local filesNo local folder access notedLOW
  • Command executionNo shell command runner notedLOW
  • Network reachLocal or standard API callsLOW
  • CredentialsNo API token requiredLOW
  • Package sourceGitHub (healthai-hq/fda-risk-radar)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

No npm or PyPI package is listed. Install from source: github.com/healthai-hq/fda-risk-radar ↗

All setup options ↓

Check this skillWatch it in my stackCompareAdd to allowlistREADME badgeView project

About Constat MCP — FDA Device Evidence Lifecycle

Constat MCP — FDA Device Evidence Lifecycle is an MCP server focused on Developer tools: FDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance.

It is hosted on GitHub at healthai-hq/fda-risk-radar. Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.

Setup

These use the package this listing points to. Check the project’s own instructions before running anything.

No npm or PyPI package is listed for this MCP server. Source code and setup steps: github.com/healthai-hq/fda-risk-radar.

Why this grade

DD — High risk signals

Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

4/100
Listing last refreshed
2026-10-28

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Security reports

No reports found for this package in our research (last checked 2026-10-29).

Check a specific version →

Risks to watch for

  • Dependency & version pinning: Distributed via GitHub (healthai-hq/fda-risk-radar). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

  • Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
  • Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

  • Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
  • If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

  • Check its activity history or logs weekly at first, and look at what it changed or sent.
  • Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

  • It asks for more access than its job requires, or prompts you to paste passwords.
  • It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

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

Constat MCP — FDA Device Evidence Lifecycle does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/healthai-hq/fda-risk-radar.

Are there security reports about Constat MCP — FDA Device Evidence Lifecycle?

No reports found for this package in our research (last checked 2026-10-29). Constat MCP — FDA Device Evidence Lifecycle currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.

Is Constat MCP — FDA Device Evidence Lifecycle actively maintained?

We do not have star or download counts on file for Constat MCP — FDA Device Evidence Lifecycle yet (listing refreshed 2026-10-28). Check the commit history and open issues at github.com/healthai-hq/fda-risk-radar before relying on it.

What are alternatives to Constat MCP — FDA Device Evidence Lifecycle?

Compare Constat MCP — FDA Device Evidence Lifecycle side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.

README badge and team notes

Maintain or use Constat MCP — FDA Device Evidence Lifecycle? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade D for Constat MCP — FDA Device Evidence Lifecycle

GitHub README Markdown:

markdown
[![AgentArmorHQ Risk Grade for Constat MCP — FDA Device Evidence Lifecycle](https://agentarmorhq.com/api/badge/healthai-hq-fda-risk-radar)](https://agentarmorhq.com/skills/healthai-hq-fda-risk-radar)

HTML embed:

html
<a href="https://agentarmorhq.com/skills/healthai-hq-fda-risk-radar"><img src="https://agentarmorhq.com/api/badge/healthai-hq-fda-risk-radar" alt="AgentArmorHQ Risk Grade for Constat MCP — FDA Device Evidence Lifecycle" height="20" /></a>

Terminal check:

terminal
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "healthai-hq-fda-risk-radar"

Share with your security lead

Need sign-off to use Constat MCP — FDA Device Evidence Lifecycle? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: Constat MCP — FDA Device Evidence Lifecycle
- **Listing URL:** https://agentarmorhq.com/skills/healthai-hq-fda-risk-radar
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** GitHub (healthai-hq/fda-risk-radar)

#### Recommended Hardened Setup
- **Source Repo:** https://github.com/healthai-hq/fda-risk-radar
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type
App connector
Publisher
healthai-hq
Source code
github.com/healthai-hq/fda-risk-radar
Est. context load
~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
Last updated
2026-10-28
Last graded
2026-10-23

Community

Discussions for Constat MCP — FDA Device Evidence Lifecycle

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for Constat MCP — FDA Device Evidence Lifecycle helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude