MCP servers · csoai-org

FDA AI/ML SaMD Compliance MCP Server

An MCP server for FDA regulatory questions about AI/ML Software as a Medical Device, covering 510(k), De Novo, PMA, PCCP and GMLP.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

The publisher marked this resource as deprecated. Prefer the alternatives below.

What it does

This MCP server covers FDA regulatory topics for AI/ML Software as a Medical Device (SaMD). The publisher lists the 510(k), De Novo and PMA pathways, along with PCCP and GMLP. The README names three tools: classify_sw_device, regulatory_pathway and pccp_template. It also states that the server includes EU AI Act compliance features referring to Articles 9, 13, 15, 26 and 50.

It suits teams building or documenting AI/ML medical software who need to classify a software device, identify a possible regulatory pathway, or work on a PCCP template. The README gives example requests that call these tools from an AI assistant.

Setup is either an entry in claude_desktop_config.json (Claude Desktop) or another MCP client configuration, or a pip installation of fda-samd-mcp followed by running the fda-samd-mcp command over stdio transport. The free tier allows 10 calls per day and needs no API key. Paid tiers add unlimited calls and signed attestations. The code is released under the MIT licence.

Limitations and requirements

The free tier is limited to 10 calls per day. Unlimited calls and signed attestations require a paid subscription. Use requires an MCP client, such as Claude Desktop, and a local Python installation if installed via pip.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CSOAI-ORG/fda-samd-mcp

    FDA AI/ML Software as a Medical Device Action Plan + 510(k) + PMA + De Novo pathways for US MedT...

    v1.0.11
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026