
catalystcal
io.github.CloudCorpRecords/catalystcal
Biotech catalyst calendar: verified PDUFA, AdComm and trial-readout dates from official sources.
Documentation
catalystcal
When is the next PDUFA date, which advisory committee meets this quarter, and what trial readouts are coming for the company or drug you follow? catalystcal is a local forwarding client for the hosted Bio Catalyst MCP service: it answers tools/list locally from the captured tool definitions and forwards every call to the service, returning the answers exactly as the service sends them back.
Every event the service returns is anchored to an official source — ClinicalTrials.gov, the Federal Register, or openFDA — and carries the source URL, the exact source field the date came from, and a verified-as-of stamp. It is a scheduling and reference dataset, not investment advice.
All 3 captured tools are built; there are no omissions.
The tools
upcoming_catalysts— The upcoming catalyst stream: trial readouts, FDA advisory-committee meetings, and recent approvals. Narrow it with adayshorizon (default 90), akindfilter (readout,adcom, orapproval), a trialphasesuch asPHASE3, a single companyticker, and alimit(default 50). No required parameters.catalyst_for_company— Every verified catalyst event for one public company, looked up by itsticker(required).catalyst_for_drug— Every verified catalyst event that references a drug or product, looked up byname(required).
Install and run
As an MCP server via npm:
npx -y @reneturcios/catalystcal mcp
MCP client configuration:
{
"mcpServers": {
"catalystcal": {
"command": "npx",
"args": ["-y", "@reneturcios/catalystcal", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/catalystcal
docker run --rm ghcr.io/cloudcorprecords/catalystcal catalyst_for_company '{"ticker":"MRNA"}'
CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
catalystcal upcoming_catalysts '{"kind":"adcom","days":60}'
catalystcal catalyst_for_company '{"ticker":"MRNA"}'
catalystcal catalyst_for_drug '{"name":"Keytruda"}'
catalystcal --version
Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
BIOCATALYST_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://biocatalyst.dropwatchhq.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with catalystcal error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
The test suite checks the served tool list against the captured surface (all 3 tools, deep-equal, in order, with no titles invented and no required key added to the tool that carries none), exercises the session handshake and its reuse, verifies that no Authorization header is ever sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
@reneturcios/catalystcalnpm install @reneturcios/catalystcalghcr.io/cloudcorprecords/catalystcal:0.1.0docker pull ghcr.io/cloudcorprecords/catalystcal:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.