Lets an assistant look up verified biotech and pharma catalyst events, such as trial readouts, FDA advisory meetings and approvals, each linked to its official.
What you can do
Provides three lookup tools over a verified catalyst calendar. upcoming_catalysts returns upcoming clinical-trial readouts, FDA AdComm meetings and recent approvals, each linked to its official source (ClinicalTrials.gov, Federal Register, openFDA) with the source URL and the exact source field the date came from. catalyst_for_company returns verified events for one public company by ticker, and catalyst_for_drug returns events referencing a drug or product name.
When to use it
Useful when tracking biotech or pharma event timelines, checking what catalysts are coming up for a ticker or drug, or grounding answers about trial and regulatory dates in official sources rather than rumor.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package, environment variables or headers are declared. No authentication is declared. Network access to the endpoint is needed.
Before you install
The company tool is described as a free preview with full data inline, so coverage or depth may be limited. Dates and events should be checked against the linked official sources before being relied on. No credentials, payments or write actions are shown.
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.dropwatchhq%2Fbio-catalyst/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.
Return upcoming biotech/pharma catalysts (clinical-trial readouts, FDA AdComm meetings, recent approvals) VERIFIED against and linked to their official source (ClinicalTrials.gov, Federal Register, openFDA). Each record includes the official sourceUrl, the exact sourceField the date came from, and a verifiedAsOf stamp. This is scheduling/reference data, NOT investment advice.
Parametersdayskindlimitphaseticker
catalyst_for_company
Return verified catalyst events for one public company by ticker, each linked to its official source. Free preview; full data inline.
Parameterstickerrequired
catalyst_for_drug
Return verified catalyst events referencing a drug/product name, each linked to its official source.
Parametersnamerequired
Version history
1
v1.0.0LatestSep 16, 2026
Score
72%
72% 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
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.