# Dataset Cleaner & Exporter (remote · dataset-cleaner-exporter.nerolabs.workers.dev)

Dedupe, flatten and clean messy JSON rows (emails, phones, URLs, HTML) in one call, as JSON or CSV.

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

## Components

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

## Channel facts

- Endpoint: `https://dataset-cleaner-exporter.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-21.

- **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 904 tokens (~452/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**: 27/100
  - Stability observed for 8 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 Cleaner & Exporter MCP server?

Dataset Cleaner & Exporter is a hosted endpoint at https://dataset-cleaner-exporter.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-cleaner-exporter 'https://dataset-cleaner-exporter.nerolabs.workers.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "nero-engine-dataset-cleaner-exporter": {
      "type": "http",
      "url": "https://dataset-cleaner-exporter.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` (~69 tokens)

Returns the exact cleaning rules (how emails, phone numbers and URLs are detected and normalized), the dedup modes and keep strategies, the order the steps run in, and the maximum rows per call. Call this first if you are unsure how a field will be treated. Free, processes no data.

### `clean_rows` (~792 tokens)

Deduplicates, flattens and cleans a list of JSON rows in one call and returns spreadsheet-ready rows (or CSV text) plus a summary with exact counts: rows in, rows added by expansion, duplicates removed, rows dropped by maxItems, rows out, the final column list, per-column fill rates and warnings. Steps, in order: optionally explode one array field into one row per entry; flatten nested objects into columns (address.city becomes address_city); trim text; lowercase valid emails; reduce phone numbers to digits with any leading +; lowercase URL hosts and drop the trailing slash; optionally strip HTML and turn numeric or true/false text into numbers and booleans; blank text becomes null; keep, remove or rename columns; then remove duplicates (normalized by default, comparing the whole row unless dedupKeys is set) keeping the most complete row. Deterministic, no AI, nothing guessed. Use it on scraped leads, CRM exports or API results before loading them anywhere. There is a row limit per call (see list_capabilities); split bigger lists across several calls.

Input parameters:

- `cleanFields` (boolean): Default true. Normalize emails, phone numbers and URLs, detected by field name or value shape.
- `coerceTypes` (boolean): Default false. Turn "42" into 42 and "true" into true. Leading-zero values like "007" stay text.
- `columnRenameMap`: Rename columns after keep/remove, as ["oldName:newName"] or {"oldName":"newName"}, for example {"Details_founded":"founded"}.
- `columnsToKeep` (array): Keep only these columns (flattened names). Takes priority over columnsToRemove.
- `columnsToRemove` (array): Drop these columns (flattened names). Ignored if columnsToKeep is set.
- `dedupKeys` (array): Fields that identify a duplicate, for example ["Email"]. Empty compares the whole row. Use the final column names: flattened (Details_founded) and renamed. Exact and case-sensitive. Rows where every…
- `dedupMode` (string): How duplicates are found. normalized (default) ignores case and whitespace; exact needs identical values; fuzzy also merges near-duplicates (up to 100 rows and 1000 characters of key text, so name a…
- `dropEmptyFields` (boolean): Default false. Remove null and empty fields from each row.
- `emptyToNull` (boolean): Default true. Blank text becomes null.
- `expandArrayField` (string): Optional. One top-level array field (for example "offers") to explode into one row per entry, repeating the other fields. Object entries become columns. The expanded total must stay within the row li…
- `flatten` (boolean): Default true. Turn nested objects into flat columns. Arrays become one JSON-text cell.
- `flattenSeparator` (string): Joins nested key paths when flattening. Default "_".
- `keepStrategy` (string): Which duplicate survives: most_complete (default, fewest empty fields), first or last.
- `maxItems` (integer): Optional cap: read at most this many rows and return at most this many. 0 (default) means no cap.
- `outputFormat` (string): json (default) returns rows; csv returns the same result as CSV text in "csv" instead.
- `rows` (array, required): The rows to clean. Each row is a JSON object; keys may differ between rows and values may be nested.
- `similarityThreshold` (number): Fuzzy mode only. 0.5 to 0.99, default 0.9. Higher is stricter.
- `stripHtml` (boolean): Default false. Remove HTML tags and decode common entities in text.

## Diagnostics

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

## Score history

- 2026-09-21: 60
- 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 Cleaner & Exporter MCP server?

Dataset Cleaner & Exporter is an MCP server listed in the public MCP registry as io.github.Nero-Engine/dataset-cleaner-exporter. Dedupe, flatten and clean messy JSON rows (emails, phones, URLs, HTML) in one call, as JSON or CSV. This page covers its hosted endpoint (https://dataset-cleaner-exporter.nerolabs.workers.dev/mcp).

### Is the Dataset Cleaner & Exporter MCP server safe to use?

Dataset Cleaner & Exporter 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 Cleaner & Exporter MCP server expose?

Dataset Cleaner & Exporter exposes 2 tools: list_capabilities, clean_rows. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.

### Does the Dataset Cleaner & Exporter MCP server require authentication?

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

### Is the Dataset Cleaner & Exporter MCP server still maintained?

Dataset Cleaner & Exporter is still listed as active in the MCP registry. We last reached this channel on 21 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-cleaner-exporter.nerolabs.workers.dev/mcp
- Repository: https://github.com/Nero-Engine/dataset-cleaner-exporter-mcp
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-dataset-cleaner-exporter/dataset-cleaner-exporter.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-dataset-cleaner-exporter/dataset-cleaner-exporter.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-dataset-cleaner-exporter/dataset-cleaner-exporter