PIASO vs Astria
PIASO is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
PIASO is a plugin bundle for AI coding tools published by Min Dai. No marketplace we read lists it any more. Astria is an MCP server published by Nodesify. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  Astria | |
|---|---|---|
| Community marketplace genecell/piaso-for-agents | Removed on 2026-10-16 Version: 0.2.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.0 Downloads/month (npm): 3 017 Downloads/week (npm): 381 Forks (GitHub): 1 Stars (GitHub): 3 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 | PIASOno longer listed · | Astria |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 3 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@nodesify/astria) |
| 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 (differs) | BSD-3-Clause | MIT |
| Repository (differs) | github.com/genecell/piaso-for-agents | github.com/nodesify/astria |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-13 | 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 PIASO
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
piaso-mcp io.github.genecell/piaso-mcp
PIASO single-cell ecosystem docs (PIASO, COSG, cytome, LARIS, cytorete) + live PIASOmarkerDB
-
life-sciences
Genomics, single-cell, proteomics, neuroscience and systems biology.
-
AI-assisted single-cell RNA-seq analysis: dataset processing, API-based cell scoring, and local model inference.
-
Guided NGS intake, local execution, and public-pipeline routing for BCL, FASTQ, DNA variant, RNA-seq, single-cell, epigenomics, amplicon, and metagenomics analyses, with deeper…
-
100+ bioinformatics Agent Skills: pharmacogenomics, clinical variant interpretation, GWAS and PRS, ancestry, RNA-seq and single-cell, metagenomics, proteomics, methylation clocks…
-
Drive SpliceCraft's plasmid workbench through its localhost agent API: annotate records, design and verify primers, simulate Golden Gate / Gibson / restriction clones…
What each says it does
PIASO
PIASO single-cell omics ecosystem: scanpy-free pipeline, marker genes (COSG/COSGR), gene-set scoring, annotation (PIASOmarkerDB), ligand-receptor (SCALAR/LARIS), regulons (cytorete), .cytome streaming, Emergene.
Astria
Turn any codebase into a queryable knowledge graph — offline-first, zero API keys.
How to run each
PIASO
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Astria As a local MCP server: npm package
claude mcp add --transport stdio astria -- npx -y @nodesify/astriaCommands 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: PIASO · What it can do: Astria · 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.