io.github.yesc97/biopharma-catalyst-mcp
NPM · BIOPHARMA-CATALYST-MCP
Forensic biopharma catalyst auditor — 10 tools, deterministic CLEAN/BEAR_SIGNAL verdict.
Available components
Last scanned (21 hours ago)
Scores higher than 62% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 46 of 140 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (ISC).Pass
- Actively maintained (last published 177 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 801 tokens (~80/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/biopharma-catalyst-mcp@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 140 packages
| Packages resolved | 140 |
|---|---|
| Deprecated | 1 |
| Stale | 45 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_catalyst ~171
FORENSIC AGGREGATOR. Runs all 8 connectors in parallel against (ticker, drug) and returns a deterministic verdict: CLEAN | FLAG | BEAR_SIGNAL | BLACK_FLAG. Encodes the full Tactical Auditor logic — terminations, FDA rejections, late-stage protocol amendments, dilution risk (runway vs catalyst), Going Concern disclosure, insider unloading, 8-K clusters, literature skepticism. CLEAN means: tried to break the thesis, couldn't. The strongest long signal this tool gives.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | yes | Drug name (brand or generic) — biopharma signal lives at the drug level, not the company level |
| sponsor | string | – | Optional sponsor company name (used for FDA fallback when drug query returns empty) |
| ticker | string | yes | The stock ticker symbol |
No output schema declared.
No examples provided.
get_fda_activity ~143
Get FDA submission and approval activity for a drug or sponsor (NDA/BLA filings, approvals, supplements). Use kind='drug' for drug name (brand or generic) or kind='sponsor' for company sponsor name. Submission status codes are decoded (AP=approved, CRL=rejection, WD=withdrawn). Supports auto-fallback from drug to sponsor if results are empty.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Whether the query is a drug name or sponsor company name |
| query | string | yes | Drug name or sponsor name to search |
| sponsorFallback | string | – | Optional: Company sponsor name to fall back to if drug search returns nothing |
No output schema declared.
No examples provided.
get_insider_transactions ~93
Get insider Form 4 transactions for a ticker over the last N days. Returns individual transactions, total sales/purchases in dollars, and a Net Insider Sentiment score (purchases - sales). Detects 10b5-1 scheduled sales but does not exempt them.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The stock ticker symbol |
| windowDays | number | – | Lookback window in days (default 90) |
No output schema declared.
No examples provided.
get_market_data ~31
Get current price and options data for a stock ticker
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The stock ticker symbol |
No output schema declared.
No examples provided.
get_protocol_snapshot ~95
Get current protocol details + amendment proximity for a clinical trial by NCT ID. Flags late-stage protocol amendments (the 'goalpost move') by computing how far into the trial timeline the last update happened. Cannot detect WHAT changed (CT.gov v2 API does not expose protocol diffs) — only WHEN.
| Name | Type | Req | Description |
|---|---|---|---|
| nctId | string | yes | ClinicalTrials.gov NCT identifier (e.g. NCT04994483) |
No output schema declared.
No examples provided.
get_sec_filings ~46
Get recent SEC filings (10-K, 10-Q, 8-K, S-1) for a stock ticker.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The stock ticker symbol |
No output schema declared.
No examples provided.
get_short_interest ~76
Get short interest data for a ticker — short % of float, days to cover, and month-over-month delta. Used to detect SHORT_INTEREST_SPIKE (delta >20%, bear) and SHORT_SQUEEZE_POTENTIAL (days to cover >5, bull).
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The stock ticker symbol |
No output schema declared.
No examples provided.
get_xbrl_facts ~69
Get structured financial facts from SEC XBRL for a ticker — cash, quarterly burn, runway months, and Going Concern disclosure flag. Used by the Tactical Auditor to detect dilution risk (runway shorter than time to next catalyst).
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The stock ticker symbol |
No output schema declared.
No examples provided.
search_clinical_trials ~42
Search ClinicalTrials.gov for studies by intervention (drug or company name)
| Name | Type | Req | Description |
|---|---|---|---|
| intervention | string | yes | The name of the drug or company to search for |
No output schema declared.
No examples provided.
search_pubmed ~35
Search PubMed for scientific papers by term (drug name, condition, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The search term |
No output schema declared.
No examples provided.
How do I install the io.github.yesc97/biopharma-catalyst-mcp server?
io.github.yesc97/biopharma-catalyst-mcp runs locally as an npm package, launched with npx -y biopharma-catalyst-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · biopharma-catalyst-mcp
claude mcp add yesc97-biopharma-catalyst-mcp -- npx -y biopharma-catalyst-mcp
What is the io.github.yesc97/biopharma-catalyst-mcp server?
io.github.yesc97/biopharma-catalyst-mcp is listed in the public MCP registry as io.github.yesc97/biopharma-catalyst-mcp. Forensic biopharma catalyst auditor, 10 tools, deterministic CLEAN/BEAR_SIGNAL verdict. This page covers its npm package (biopharma-catalyst-mcp).
Is the io.github.yesc97/biopharma-catalyst-mcp server safe to use?
io.github.yesc97/biopharma-catalyst-mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.yesc97/biopharma-catalyst-mcp server expose?
io.github.yesc97/biopharma-catalyst-mcp exposes 10 tools: search_clinical_trials, search_pubmed, get_sec_filings, get_market_data, get_fda_activity, and 5 more. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.
Is the io.github.yesc97/biopharma-catalyst-mcp server still maintained?
io.github.yesc97/biopharma-catalyst-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.yesc97/biopharma-catalyst-mcp server under?
io.github.yesc97/biopharma-catalyst-mcp declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.