Clinical Fda Mcp

io.github.sercanmetalorePublished by GitHub account sercanmetalorev0.1.0Updated Oct 24, 2026

openFDA ilaç geri çağırma kayıtları + ClinicalTrials.gov klinik deney arama, ABD federal açık…

The publisher's own server: [PREPROD] Clinical.ly Research Suite

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

A remote MCP server that lets an assistant search openFDA drug recall records and ClinicalTrials.gov clinical trial listings.

What you can do
Search openFDA drug recall records and look up recall details from US federal open data sources. Search ClinicalTrials.gov for clinical trial listings. Combine recall and trial lookups when researching a drug or condition.
When to use it
Useful when you need quick lookups of US drug recall history or clinical trial registrations, for example during pharmacovigilance research, regulatory background checks, or patient-facing information gathering.
Requirements
A remote streamable HTTP endpoint; no local runtime, account, API key, or environment variables are declared. Network access to the hosted endpoint is required.
Before you install
Queries are sent to a third-party hosted endpoint, not directly to the government sources. The data covers US federal open datasets only and may be incomplete or outdated; verify results against official openFDA and ClinicalTrials.gov records before relying on them.

Installation

In SourceWeft

  1. Open Clinical Fda Mcp 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/io.github.sercanmetalore%2Fclinical-fda-mcp/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": {
    "clinical-fda": {
      "type": "http",
      "url": "https://mcp.boykaf.com/clinical-fda/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.0LatestSep 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 Clinical integrations