Ext Ops Panel
Open dashboard
Comparison

BioAI 日知 vs io.github.yesc97/biopharma-catalyst-mcp

BioAI 日知 is an MCP server published by MInsYang. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.yesc97/biopharma-catalyst-mcp is an MCP server published by yesc97. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceBioAI 日知io.github.yesc97/biopharma-catalyst-mcp
Official MCP Registry Listed
Version: 3.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.2.0
Downloads/month (npm): 161
Downloads/week (npm): 35
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

BioAI 日知 vs io.github.yesc97/biopharma-catalyst-mcp
FactBioAI 日知io.github.yesc97/biopharma-catalyst-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)5 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (bioai-rizhi.pages.dev/mcp)On your machine (biopharma-catalyst-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/minsyang/bioai-rizhigithub.com/yesc97/biopharma-catalyst-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

BioAI 日知

In its own words, on Official MCP Registry:

Read-only AI biopharma news, research records, companies, and source status from BioAI 日知.

io.github.yesc97/biopharma-catalyst-mcp

In its own words, on Official MCP Registry:

Forensic biopharma catalyst auditor — 10 tools, deterministic CLEAN/BEAR_SIGNAL verdict.

How to run each

BioAI 日知 As a remote MCP server

Claude Code
claude mcp add --transport http bioai-rizhi https://bioai-rizhi.pages.dev/mcp

io.github.yesc97/biopharma-catalyst-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SEC_USER_AGENT=<YOUR_SEC_USER_AGENT>" --transport stdio biopharma-catalyst-mcp -- npx -y biopharma-catalyst-mcp

Requires: SEC_USER_AGENT

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only BioAI 日知 has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of BioAI 日知 publish no settings it asks for, so we do not compare settings.

What it can do: BioAI 日知 · What it can do: io.github.yesc97/biopharma-catalyst-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built