# Dataset Filter & Transform (remote · dataset-filter-transform.nerolabs.workers.dev)

Clean, filter and reshape JSON rows in one call: 26 transforms, 25 filters, sort, dedupe, limit.

- Trust score: 60/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `dataset-filter-transform.nerolabs.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/nero-engine-dataset-filter-transform/dataset-filter-transform.md), [page](https://verifymcp.io/servers/nero-engine-dataset-filter-transform/dataset-filter-transform)

## Channel facts

- Endpoint: `https://dataset-filter-transform.nerolabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 555 tokens (~277/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Dataset Filter & Transform MCP server?

Dataset Filter & Transform is a hosted endpoint at https://dataset-filter-transform.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.

### Claude

```bash
claude mcp add --transport http nero-engine-dataset-filter-transform 'https://dataset-filter-transform.nerolabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nero-engine-dataset-filter-transform": {
      "url": "https://dataset-filter-transform.nerolabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nero-engine-dataset-filter-transform": {
      "type": "http",
      "url": "https://dataset-filter-transform.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nero-engine-dataset-filter-transform]
url = "https://dataset-filter-transform.nerolabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-dataset-filter-transform": {
      "type": "remote",
      "url": "https://dataset-filter-transform.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nero-engine-dataset-filter-transform --url 'https://dataset-filter-transform.nerolabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nero-engine-dataset-filter-transform:
    url: "https://dataset-filter-transform.nerolabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nero-engine-dataset-filter-transform": {
      "Transport": "http",
      "Url": "https://dataset-filter-transform.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nero-engine-dataset-filter-transform -t streamable-http -u 'https://dataset-filter-transform.nerolabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nero-engine-dataset-filter-transform": {
      "type": "http",
      "url": "https://dataset-filter-transform.nerolabs.workers.dev/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 60, +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.

### 2026-09-18 (score 59, +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.

### 2026-09-16 (score 58, +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.

### 2026-09-14 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 57)

First indexed and scored.

## MCP tools (2)

### `list_capabilities` (~51 tokens)

Returns every filter operator and transform operation this server supports, the order the pipeline runs in, and the maximum rows per call. Call this first if you are unsure what is available. Free, processes no data.

### `process_rows` (~473 tokens)

Cleans a list of JSON rows in one call: transforms each row, filters out the rows you do not want, then optionally sorts, de-duplicates and limits them. Returns the kept rows plus a summary of exactly what was removed and why. Use it to reshape scraped or API data before passing it on: rename and drop fields, cast strings to numbers, compute new fields with arithmetic, extract with regex, then keep only the rows that match your rules. Transforms run before filters, so you can filter on a field you just created.

Input parameters:

- `caseSensitiveFilters` (boolean): Text comparisons are case-insensitive by default. Set true to make them exact.
- `distinctBy` (array): Keep only the first row for each combination of these fields. Applied after sorting, so sorting first lets you keep the newest row per key.
- `filterCombineMode` (string): Whether a row must match every filter (AND, the default) or any one of them (OR).
- `filters` (array): Conditions a row must satisfy to be kept, for example {"field":"country","operator":"equals","value":"UK"} or {"field":"price","operator":"greaterThan","value":100}. Dot paths like "address.city" wor…
- `lenientNumbers` (boolean): On by default: values like "$1,234.50", "49 USD" and "12%" are read as numbers. Set false to require real numeric values.
- `limit` (integer): Return at most this many rows.
- `offset` (integer): Skip this many rows after filtering and sorting.
- `rows` (array, required): The rows to process. Each row is a JSON object. Keys may differ between rows.
- `sortBy` (array): Sort the kept rows, for example [{"field":"price","direction":"desc"}].
- `transforms` (array): Transform steps applied to every row, in order. Each step is an object with an "op" key, for example {"op":"cast","field":"price","to":"number"} or {"op":"compute","field":"total","expression":"price…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nero-engine-dataset-filter-transform/dataset-filter-transform#diagnostics

## Score history

- 2026-09-20: 60
- 2026-09-19: 59
- 2026-09-18: 59
- 2026-09-17: 58
- 2026-09-16: 58
- 2026-09-15: 57
- 2026-09-14: 57
- 2026-09-13: 57

## Common questions

### What is the Dataset Filter & Transform MCP server?

Dataset Filter & Transform is an MCP server listed in the public MCP registry as io.github.Nero-Engine/dataset-filter-transform. Clean, filter and reshape JSON rows in one call: 26 transforms, 25 filters, sort, dedupe, limit. This page covers its hosted endpoint (https://dataset-filter-transform.nerolabs.workers.dev/mcp).

### Is the Dataset Filter & Transform MCP server safe to use?

Dataset Filter & Transform scores 60 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 Filter & Transform MCP server expose?

Dataset Filter & Transform exposes 2 tools: list_capabilities, process_rows. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.

### Does the Dataset Filter & Transform MCP server require authentication?

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

### Is the Dataset Filter & Transform MCP server still maintained?

Dataset Filter & Transform 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.

## Links

- Remote endpoint: https://dataset-filter-transform.nerolabs.workers.dev/mcp
- Repository: https://github.com/Nero-Engine/dataset-filter-transform-mcp
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-dataset-filter-transform/dataset-filter-transform.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-dataset-filter-transform/dataset-filter-transform.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-dataset-filter-transform/dataset-filter-transform