bio-catalyst MCP server
com.dropwatchhq/bio-catalystdropwatchhq.comstreamable-httpv1.0.0Scanned
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
3 tools: 3 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the bio-catalyst MCP server can do
The bio-catalyst MCP server is published by dropwatchhq.com, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (upcoming_catalysts).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
catalyst_for_companyReturn verified catalyst events for one public company by ticker, each linked to its official source.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return verified catalyst events for one public company by ticker, each linked to its official source. Free preview; full data inline.
catalyst_for_drugReturn verified catalyst events referencing a drug/product name, each linked to its official source.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return verified catalyst events referencing a drug/product name, each linked to its official source.
upcoming_catalystsReturn upcoming biotech/pharma catalysts (clinical-trial readouts, FDA AdComm meetings, recent approvals) VERIFIED against and linked to their official source (ClinicalTrials.gov, …Reads private dataNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "meeting": it reads calendars.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bio-catalyst https://biocatalyst.dropwatchhq.com/mcpclaude mcp add --transport http bio-catalyst https://biocatalyst.dropwatchhq.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bio-catalyst__upcoming_catalysts",
"mcp__bio-catalyst__catalyst_for_company",
"mcp__bio-catalyst__catalyst_for_drug"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bio-catalyst. Review it before you use it.
Capability tags behind 1 rule
- mcp__bio-catalyst__upcoming_catalysts private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.dropwatchhq/bio-catalyst/verify?hash=00bda22e197aaac2fb92156ae7fbe81369a4a8e12c9c93f9e9a8b92a2f7f2d65" | jq -e '.changed == false'Pinned hash 00bda22e197a, from Nov 17, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.dropwatchhq/bio-catalyst/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.dropwatchhq/bio-catalyst)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
bio-catalyst MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the bio-catalyst MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the bio-catalyst MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the bio-catalyst MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the bio-catalyst MCP server have?
- 3 tools: 3 read. upcoming_catalysts, catalyst_for_company and catalyst_for_drug.
Does the bio-catalyst MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the bio-catalyst MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the bio-catalyst MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.