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.

Dataset Aggregate & Pivot

REMOTE · DATASET-AGGREGATE-PIVOT.NEROLABS.WORKERS.DEV · SCANNED SEP 20

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

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

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 886 tokens (~443/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Dataset Aggregate & Pivot MCP server?

Dataset Aggregate & Pivot is a hosted endpoint at https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · dataset-aggregate-pivot.nerolabs.workers.dev

# add to Claude Code
claude mcp add --transport http nero-engine-dataset-aggregate-pivot 'https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nero-engine-dataset-aggregate-pivot": {
      "url": "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nero-engine-dataset-aggregate-pivot": {
      "type": "http",
      "url": "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nero-engine-dataset-aggregate-pivot]
url = "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-dataset-aggregate-pivot": {
      "type": "remote",
      "url": "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nero-engine-dataset-aggregate-pivot --url 'https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nero-engine-dataset-aggregate-pivot:
    url: "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nero-engine-dataset-aggregate-pivot": {
      "Transport": "http",
      "Url": "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nero-engine-dataset-aggregate-pivot -t streamable-http -u 'https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "nero-engine-dataset-aggregate-pivot": {
      "type": "http",
      "url": "https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 13 Sept 26 55

    First indexed and scored.

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 · Probed https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nerolabs.workers.dev CN=YE2,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 6f7f02a43942bb2aca3c411aec703cf0dc1
SANs: *.nerolabs.workers.dev, nerolabs.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dataset-aggregate-pivot.nerolabs.workers.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp Verified 200
http (plaintext) http://dataset-aggregate-pivot.nerolabs.workers.dev/mcp Inconclusive 405
MCP tools · 2 exposed · ~839 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
aggregate_rows ~767

SQL GROUP BY and a spreadsheet pivot table for a list of JSON rows, in one call. Returns one output row per group with the aggregated columns, plus a summary: groups found, groups dropped by topN, values skipped because they were blank or not numeric (never guessed), and warnings such as a misspelled field name. Use it to turn scraped or API records into totals: orders and revenue per region, average price per brand, listings per city per month, top 10 products by revenue. Messy data is expected: "South" and "south " group together, and "$1,234.50" sums as 1234.5. Leave groupByFields empty to summarise all rows into one row. At most 500 rows per call.

NameTypeReqDescription
aggregationsarrayWhat to compute per group, for example [{"function":"count","alias":"orders"}, {"field":"amount","function":"sum","alias":"total_amount"}]. Every function except count needs a field. alias is the out…
dateBucketFieldstringA date or timestamp field to group by time period, for example "orderedAt". Adds a group column named like "orderedAt_month". Unreadable dates land in an "(invalid date)" group.
dateBucketGranularitystringBucket size for dateBucketField: day (2026-08-19), week (2026-W34), month (2026-08, default), quarter (2026-Q3) or year.
groupByFieldsarrayOne output row per distinct combination of these field values, like SQL GROUP BY, for example ["region"] or ["city", "category"]. Dot paths like "address.city" work. Empty or omitted aggregates every…
groupMatchingstringnormalized (default) ignores letter case and extra whitespace when grouping, so "South" and "south " are one group. exact requires identical values.
includeTotalsRowbooleanAppends a grand-total row labelled "(total)" and adds a _rowType column ("group" or "total").
lenientNumbersbooleanOn by default: "$1,234.50", "49 USD", "12%" and "(300)" count as numbers for sum, avg, min, max and median. Set false to accept only real numbers and plain numeric strings.
pivotFieldstringTurns this field's distinct values into columns, pivot-table style: group by "region" and pivot on "product" for one row per region with a column per product. Must not also be a group-by field. At mo…
pivotFunctionstringHow pivot cell values are combined. Defaults to sum when pivotValueField is set; ignored (row count) without one.
pivotValueFieldstringThe field whose values fill the pivot cells, for example "amount". Omitted fills each cell with a row count.
rowsarrayyesThe records to aggregate, up to 500. Each row is a JSON object; keys may differ between rows.
sortBystringAn output column to sort by: a group field, an aggregation alias such as "total_amount", or a pivot column. Omitted sorts by the group fields.
sortDirectionstringasc (default) or desc. Use desc with topN for "top N by" questions.
topNintegerAfter sorting, keep only the first N groups. The totals row still covers every input row.

No output schema declared.

No examples provided.

list_capabilities ~72

Returns the 11 aggregation functions and what each one does, the date bucket formats, the labels used for blank, invalid-date and total rows, and the limits per call (rows, pivot columns, pivot cells, aggregations). Call this first if you are unsure what is available. Free, processes no data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Dataset Aggregate & Pivot MCP server?

Dataset Aggregate & Pivot is an MCP server listed in the public MCP registry as io.github.Nero-Engine/dataset-aggregate-pivot. GROUP BY and pivot tables for JSON rows: 11 functions, date buckets, top N, totals, messy numbers. This page covers its hosted endpoint (https://dataset-aggregate-pivot.nerolabs.workers.dev/mcp).

Is the Dataset Aggregate & Pivot MCP server safe to use?

Dataset Aggregate & Pivot scores 59 out of 100 on VerifyMCP. 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 Dataset Aggregate & Pivot MCP server expose?

Dataset Aggregate & Pivot exposes 2 tools: list_capabilities, aggregate_rows. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.

Does the Dataset Aggregate & Pivot MCP server require authentication?

No. We connected to Dataset Aggregate & Pivot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Dataset Aggregate & Pivot MCP server still maintained?

Dataset Aggregate & Pivot 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.