Ext Ops Panel
Open dashboard
Comparison

io.github.cyanheads/chembl-mcp-server vs Biomedical Data

io.github.cyanheads/chembl-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). Biomedical Data is an MCP server published by memoryapi.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplaceio.github.cyanheads/chembl-mcp-serverBiomedical Data
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 1 215
Downloads/week (npm): 344
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

io.github.cyanheads/chembl-mcp-server vs Biomedical Data
Factio.github.cyanheads/chembl-mcp-serverBiomedical Data
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-18Not published
Where it runs (differs)Remote server (chembl.caseyjhand.com/mcp)Remote server (bio.memoryapi.org/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)15, secrets among them: 0Not published
LicenceNot statedNot stated
Repository (differs)github.com/cyanheads/chembl-mcp-serverNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 1 h agoResponded 3 days ago

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

io.github.cyanheads/chembl-mcp-server

In its own words, on Official MCP Registry:

Link compounds to protein targets, rank bioactivity, and look up drug mechanisms and indications.

Biomedical Data

In its own words, on Official MCP Registry:

Biomedical data: compounds, drug info, and molecular targets

How to run each

io.github.cyanheads/chembl-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http chembl-mcp-server https://chembl.caseyjhand.com/mcp

Biomedical Data As a remote MCP server

Claude Code
claude mcp add --transport http bio https://bio.memoryapi.org/mcp

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

Both endpoints responded at the last daily 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 Biomedical Data publish no settings it asks for, so we do not compare settings.

What it can do: io.github.cyanheads/chembl-mcp-server · What it can do: Biomedical Data · 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