warpio vs BioHarbor
warpio is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
warpio is a plugin bundle for AI coding tools published by IOWarp.ai. No marketplace we read lists it any more. BioHarbor is an MCP server published by danielLuo2. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  BioHarbor | |
|---|---|---|
| Community marketplace akougkas/claude-code-4-science | 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: 0.1.6 Downloads/month (PyPI): 521 Downloads/week (PyPI): 446 Forks (GitHub): 0 Stars (GitHub): 0 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 | warpiono longer listed · | BioHarbor |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (bioharbor) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 10, secrets among them: 3 | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 52 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/akougkas/claude-code-4-science | github.com/danielluo2/bioharbor |
| Changes in the last 7 days (differs) | 2 | 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 warpio
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Arquestra — Scientific Computing Orchestration
AI orchestration for computational chemistry and HPC workflows.
-
Automated AI research toolkit: hypothesis generation, experiments, and paper writing
-
Skills for NVIDIAs ecosystem spans GPU acceleration, CUDA, AI agents, inference, robotics, Physical AI, Omniverse, and simulation. This plugin helps you understand the pieces…
-
Find the right NVIDIA skill for GPU acceleration, CUDA, AI agents, data loading, training, inference, robotics, Physical AI, Omniverse, simulation, and other NVIDIA-powered…
-
Full Domino Data Lab platform support — workspaces, jobs, model deployment, experiment tracking, GenAI tracing, Spark/Ray/Dask, and app deployment for data science teams
-
Discover, run, inspect, build, test, and privately reuse AI workflows.
What each says it does
warpio
Complete scientific computing orchestration with 13 AI experts (5 core + 8 specialized), 17 MCP tools, and HPC automation
BioHarbor
Run real bioinformatics from your AI agent. Reliable, reproducible, on your own GPUs.
How to run each
warpio
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BioHarbor As a local MCP server: PyPI package
claude mcp add --transport stdio bioharbor -- uvx bioharbor serveCommands 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 BioHarbor publish no settings it asks for, so we do not compare settings.
What it can do: warpio · What it can do: BioHarbor · 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.