Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.genecell/piaso-mcp

PYPI · PIASO-MCP · SCANNED SEP 20

PIASO single-cell ecosystem docs (PIASO, COSG, cytome, LARIS, cytorete) + live PIASOmarkerDB

Available components

+4 this week 58 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 872 tokens (~72/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.genecell/piaso-mcp server?

io.github.genecell/piaso-mcp runs locally as a PyPI package, launched with uvx piaso-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · piaso-mcp

# add to Claude Code
claude mcp add genecell-piaso-mcp -- uvx piaso-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "genecell-piaso-mcp": {
      "command": "uvx",
      "args": [
        "piaso-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "genecell-piaso-mcp": {
      "command": "uvx",
      "args": [
        "piaso-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add genecell-piaso-mcp -- uvx piaso-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "genecell-piaso-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "piaso-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add genecell-piaso-mcp --command uvx --arg piaso-mcp
# ~/.hermes/config.yaml
mcp_servers:
  genecell-piaso-mcp:
    command: "uvx"
    args: ["piaso-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "genecell-piaso-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "piaso-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add genecell-piaso-mcp -t stdio -c uvx -a piaso-mcp
// mcp.json
{
  "mcpServers": {
    "genecell-piaso-mcp": {
      "command": "uvx",
      "args": [
        "piaso-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 0
    • Package version: 0.0.2 → 0.1.0 functional
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −15
    • Malware scan: pass → unverified security
  • 16 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 −12
    • Malware scan: pass → unverified security
    • Stability: unverified → 0.27 functional
  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/piaso-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~872 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_versions ~57

Current PyPI release of each Python package vs the version this snapshot was tested against. Pure PyPI JSON (network); use it to disclose drift ('docs tested on 1.2.3, you have 1.3.0').

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

compare_implementations ~62

COSG (Python) vs COSGR (R) divergences — params, defaults, data-object contract — and, for 'cytome', the Python vs R cytome packages. This knowledge exists nowhere else.

NameTypeReqDescription
functionstring
NameTypeReqDescription
resultstringyes

No examples provided.

get_api ~87

Data-object contract (reads/writes, defaults, what it computes) for a PIASO / COSG / cytome / LARIS / Emergene / cytorete function, from the component docs. The exact live signature is on the generated API reference at https://piaso.org/api/ (or `inspect.signature` after install).

NameTypeReqDescription
functionstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_dataset ~48

One PIASO-data registry entry (live): title, url, md5, size, cells, features, counts layer, reference, tutorials that use it.

NameTypeReqDescription
namestringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_markers ~48

Alias of query_marker_db (mirrors piaso.tl.getMarkers).

NameTypeReqDescription
cell_type
gene
limitinteger
species
NameTypeReqDescription
resultstringyes

No examples provided.

list_datasets ~58

PIASO-data datasets (live registry from genecell/PIASO-data, cached 24 h): id, format, size, species, cells, counts layer, how to load. Falls back to the bundled data.md offline.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

list_studies ~32

List the studies available in PIASOmarkerDB (proxies the live API; 36 at last check).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

list_tutorials ~120

The piaso.org tutorial index (executed, human-reviewed): title, URL, what it covers, which components it uses. Filter by topic (scRNA-seq, methods, marker-genes, annotation, gene-sets, spatial, grn, cell-cell-interaction, plotting-data) and/or component (piaso, cosg, cytome, laris, cytorete, emergene). Route the user to the tutorial for their platform before writing code.

NameTypeReqDescription
component
topic
NameTypeReqDescription
resultstringyes

No examples provided.

query_marker_db ~133

Query the live PIASOmarkerDB for cell-type marker genes (proxies the piaso.org REST API). Works with zero packages installed, and is the programmatic path for R / non-Python users. Returns rows with: cell_type, condition, gene, species, specificity_score (a COSG score), study_publication, tissue. Cell-type names must match the study's vocabulary exactly. Requires network access to piaso.org.

NameTypeReqDescription
cell_type
gene
limitinteger
species
study
tissue
NameTypeReqDescription
resultstringyes

No examples provided.

resolve_install ~84

The exact install line(s) for a set of components in a given language (python|r), including extras. Answers 'I'm in R and want this chain — what do I install?' — the most error-prone thing in an independently-installed, cross-language ecosystem. Never suggests a matplotlib pin.

NameTypeReqDescription
componentsarrayyes
languagestring
NameTypeReqDescription
resultstringyes

No examples provided.

search_docs ~102

Search the PIASO ecosystem knowledge pack (works with zero packages installed). Covers PIASO, COSG/COSGR, cytome (Python + R), LARIS, Emergene, cytorete, PIASO-data, the cross-component decision rules, gotchas and the piaso.org tutorial index. Returns the most relevant sections for `query`.

NameTypeReqDescription
max_resultsinteger
querystringyes
NameTypeReqDescription
resultstringyes

No examples provided.

version_matrix ~41

The component versions this knowledge pack was tested against (from meta.yaml), with install lines, roles and citations — so an agent can state what the docs assume.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.genecell/piaso-mcp server?

io.github.genecell/piaso-mcp is listed in the public MCP registry as io.github.genecell/piaso-mcp. PIASO single-cell ecosystem docs (PIASO, COSG, cytome, LARIS, cytorete) + live PIASOmarkerDB. This page covers its PyPI package (piaso-mcp).

Is the io.github.genecell/piaso-mcp server safe to use?

io.github.genecell/piaso-mcp scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.genecell/piaso-mcp server expose?

io.github.genecell/piaso-mcp exposes 12 tools: search_docs, get_api, compare_implementations, resolve_install, list_tutorials, and 7 more. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.

Is the io.github.genecell/piaso-mcp server still maintained?

io.github.genecell/piaso-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.