BioSymphony BioProspector vs io.github.mims-harvard/tooluniverse
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. io.github.mims-harvard/tooluniverse is an MCP server published by mims-harvard. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. 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 |  io.github.mims-harvard/tooluniverse | |
|---|---|---|
| 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: 1.5.7 Downloads/month (PyPI): 40 535 Downloads/week (PyPI): 15 633 Forks (GitHub): 269 Stars (GitHub): 1 762 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 · | io.github.mims-harvard/tooluniverse |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 2 | 1 762 |
| Forks (GitHub) (differs) | 1 | 269 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (tooluniverse) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 16 |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | 1 | 174 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/biosymphony/bioprospector | github.com/mims-harvard/tooluniverse |
| Changes in the last 7 days (differs) | 0 | 1 |
| 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.
-
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.
-
Corollary — scientific AI models, tools and databases
Find open biology and chemistry AI models, bioinformatics tools and databases, and run them online.
-
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.
-
Biotech intelligence for AI agents: drugs, targets, diagnostics, PoS estimates, and writeups.
What each says it does
BioSymphony BioProspector
Plan public-safe biosynthetic pathway discovery campaigns.
io.github.mims-harvard/tooluniverse
2,700+ scientific tools for AI scientists: life science, research, literature, and more.
How to run each
BioSymphony BioProspector
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.mims-harvard/tooluniverse As a local MCP server: PyPI package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "AZURE_OPENAI_API_KEY=<YOUR_AZURE_OPENAI_API_KEY>" --env "BIOGRID_API_KEY=<YOUR_BIOGRID_API_KEY>" --env "BRENDA_PASSWORD=<YOUR_BRENDA_PASSWORD>" --env "DISGENET_API_KEY=<YOUR_DISGENET_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "HF_TOKEN=<YOUR_HF_TOKEN>" --env "NCBI_API_KEY=<YOUR_NCBI_API_KEY>" --env "NVIDIA_API_KEY=<YOUR_NVIDIA_API_KEY>" --env "OMIM_API_KEY=<YOUR_OMIM_API_KEY>" --env "ONCOKB_API_TOKEN=<YOUR_ONCOKB_API_TOKEN>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "SEMANTIC_SCHOLAR_API_KEY=<YOUR_SEMANTIC_SCHOLAR_API_KEY>" --env "UMLS_API_KEY=<YOUR_UMLS_API_KEY>" --env "USPTO_API_KEY=<YOUR_USPTO_API_KEY>" --transport stdio tooluniverse -- uvx tooluniverse tooluniverse-smcp-stdio --compact-modeRequires: ANTHROPIC_API_KEY (secret), AZURE_OPENAI_API_KEY (secret), BIOGRID_API_KEY (secret), BRENDA_PASSWORD (secret), DISGENET_API_KEY (secret), GEMINI_API_KEY (secret), HF_TOKEN (secret), NCBI_API_KEY (secret), NVIDIA_API_KEY (secret), OMIM_API_KEY (secret), ONCOKB_API_TOKEN (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), SEMANTIC_SCHOLAR_API_KEY (secret), UMLS_API_KEY (secret), USPTO_API_KEY (secret)
Commands 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
The marketplaces of BioSymphony BioProspector publish no settings it asks for, so we do not compare settings.
What it can do: BioSymphony BioProspector · What it can do: io.github.mims-harvard/tooluniverse · 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.