BioSymphony BioProspector vs BioMASS ODE Model Builder
BioSymphony BioProspector is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
BioSymphony BioProspector is a plugin bundle for AI coding tools published by BioSymphony. No marketplace we read lists it any more. BioMASS ODE Model Builder is an MCP server published by marcorusc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  BioMASS ODE Model Builder | |
|---|---|---|
| Community marketplace biosymphony/bioprospector | Removed on 2026-10-17 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.4.0 Downloads/month (PyPI): 1 519 Downloads/week (PyPI): 97 Forks (GitHub): 6 Stars (GitHub): 19 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
| Fact | BioSymphony BioProspectorno longer listed · | BioMASS ODE Model Builder |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 19 |
| Forks (GitHub) (differs) | 1 | 6 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-biomodelling-servers) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/biosymphony/bioprospector | github.com/marcorusc/mcp-biomodelling-servers |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of BioSymphony BioProspector
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Plan public-safe biosynthetic gene-cluster campaigns.
-
Plan public-safe structural biology campaigns.
-
197 ready-to-use life sciences skills that turn Claude into a domain expert for genomics, proteomics, drug discovery, biostatistics, scientific computing, and scientific writing…
-
Predict structures, screen molecules and proteins, and design binders.
-
Connect to preclinical research tools and databases (literature search, genomics analysis, target prioritization) to accelerate early-stage life sciences R&D
-
Predict structures, screen molecules and proteins, and design binders with Boltz from Claude Code.
What each says it does
BioSymphony BioProspector
Plan public-safe biosynthetic pathway discovery campaigns.
BioMASS ODE Model Builder
Construct, inspect, visualize, and simulate evidence-backed ODE models with BioMASS
How to run each
BioSymphony BioProspector
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BioMASS ODE Model Builder As a local MCP server: PyPI package
claude mcp add --transport stdio biomass -- uvx --from mcp-biomodelling-servers==2.4.0 mcp-biomass-server mcp-biomodelling-serversCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: BioSymphony BioProspector · What it can do: BioMASS ODE Model Builder · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.