Dataset Filter & Transform is an MCP server published by io.github.Nero-Engine, hosted at dataset-filter-transform.nerolabs.workers.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including list_capabilities, process_rows.
Clean, filter and reshape JSON rows in one call: 26 transforms, 25 filters, sort, dedupe, limit.
117 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
No parameters.
{
"name": "list_capabilities",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
}
}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.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Parameter | Type | Description |
|---|---|---|
| rows * | array | The rows to process. Each row is a JSON object. Keys may differ between rows. |
| limit | integer | Return at most this many rows. |
| offset | integer | Skip this many rows after filtering and sorting. |
| sortBy | array | Sort the kept rows, for example [{"field":"price","direction":"desc"}]. |
| 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" work. Call list_capabilities for all 25 operators. |
| 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. |
| 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 * qty"} or {"op":"rename","from":"e_mail","to":"email"}. Call list_capabilities for all 26 operation… |
| 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. |
| filterCombineMode | string | Whether a row must match every filter (AND, the default) or any one of them (OR). |
| caseSensitiveFilters | boolean | Text comparisons are case-insensitive by default. Set true to make them exact. |
{
"name": "process_rows",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"rows"
],
"properties": {
"rows": {
"type": "array",
"items": {
"type": "object"
},
"description": "The rows to process. Each row is a JSON object. Keys may differ between rows."
},
"limit": {
"type": "integer",
"description": "Return at most this many rows."
},
"offset": {
"type": "integer",
"description": "Skip this many rows after filtering and sorting."
},
"sortBy": {
"type": "array",
"items": {
"type": "object"
},
"description": "Sort the kept rows, for example [{\"field\":\"price\",\"direction\":\"desc\"}]."
},
"filters": {
"type": "array",
"items": {
"type": "object"
},
"description": "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\" work. Call list_capabilities for all 25 operators."
},
"distinctBy": {
"type": "array",
"items": {
"type": "string"
},
"description": "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."
},
"transforms": {
"type": "array",
"items": {
"type": "object"
},
"description": "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 * qty\"} or {\"op\":\"rename\",\"from\":\"e_mail\",\"to\":\"email\"}. Call list_capabilities for all 26 operations."
},
"lenientNumbers": {
"type": "boolean",
"description": "On by default: values like \"$1,234.50\", \"49 USD\" and \"12%\" are read as numbers. Set false to require real numeric values."
},
"filterCombineMode": {
"enum": [
"AND",
"OR"
],
"type": "string",
"description": "Whether a row must match every filter (AND, the default) or any one of them (OR)."
},
"caseSensitiveFilters": {
"type": "boolean",
"description": "Text comparisons are case-insensitive by default. Set true to make them exact."
}
},
"additionalProperties": false
}
}Call list_capabilities to see every filter operator and transform operation, then process_rows to clean a list of JSON rows in a single call.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.