Ext Ops Panel
Open dashboard
Comparison

Dataset Aggregate & Pivot vs CLIO Adios

Dataset Aggregate & Pivot is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). CLIO Adios is an MCP server published by iowarp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceDataset Aggregate & PivotCLIO Adios
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.2.6
Downloads/month (PyPI): 2 681
Downloads/week (PyPI): 4 590
Forks (GitHub): 25
Stars (GitHub): 30
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

Dataset Aggregate & Pivot vs CLIO Adios
FactDataset Aggregate & PivotCLIO Adios
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)30 (better)
Forks (GitHub) (differs)0 (worse)25 (better)
Last release (differs)Not published2026-10-28
Where it runs (differs)Remote server (dataset-aggregate-pivot.nerolabs.workers.dev/mcp)On your machine (clio-kit)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/nero-engine/dataset-aggregate-pivot-mcpgithub.com/iowarp/clio-kit
Changes in the last 7 days (differs)020 or more
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Dataset Aggregate & Pivot

In its own words, on Official MCP Registry:

GROUP BY and pivot tables for JSON rows: 11 functions, date buckets, top N, totals, messy numbers.

CLIO Adios

In its own words, on Official MCP Registry:

Fetch and analyze BP5 data files using ADIOS2. Access scientific data, metadata, and attributes...

How to run each

Dataset Aggregate & Pivot As a remote MCP server

Claude Code
claude mcp add --transport http dataset-aggregate-pivot https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp

CLIO Adios As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio adios-mcp -- uvx clio-kit mcp-server adios

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Dataset Aggregate & Pivot has a remote endpoint we check. How we check endpoints

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: Dataset Aggregate & Pivot · What it can do: CLIO Adios · Compare two other plugins

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.

Where the data comes from: how the catalog is built