Dataset Diff & Change Detector MCP server
online · 100% uptimeio.github.Nero-Engine/dataset-diff-detector·v0.1.0Compare two versions of a JSON row list: what was added, removed or changed, field by field.
0 stars
Reviews
Write oneNobody has reviewed Dataset Diff & Change Detector yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Dataset Diff & Change Detector tools (2)
write = sends, deletes, buys or postsdiff_rowsFreeCompares two versions of the same list of JSON rows (a before and an after snapshot, such as yesterday's and today's price list, product feed or CRM export) and returns one row per difference: status added, removed or changed, the key, the old and new values, and changedFields naming exactly which fields moved. Set keyFields to the field(s) that identify a row (sku, id, email); without it rows match on full content and an edited row shows as removed plus added. Comparison is exact: "19.99" (text) and 19.99 (a number) differ, as do "Blue" and "blue " and null and a missing field; nested objects compare by value. Put always-changing fields such as timestamps in ignoreFields. The summary counts added, removed, changed and unchanged rows and warns about duplicate keys, rows missing a key, and field names found in no row. oldRows and newRows together are limited per call (list_capabilities gives the number); larger calls are refused with a message saying how to split them.
list_capabilitiesFreeReturns the exact matching and comparison rules diff_rows uses, the shape and order of its output rows, and the maximum rows per call. Call this first if you are unsure how values are compared. Free, processes no data.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 161ms20/20
- Tool poisoning2 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 21 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Dataset Diff & Change Detector compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 37 ms
- faster than 94% of 30,031 servers
What its tools let an agent do: 2 read
Install Dataset Diff & Change Detector in Claude Code, Cursor or VS Code
claude mcp add --transport http dataset-diff-detector https://dataset-diff-detector.nerolabs.workers.dev/mcp
What the publisher says
From the Dataset Diff & Change Detector repository's README, as published. We do not edit it. Read it on GitHub
Dataset Diff & Change Detector (Remote MCP Server)
Compare two versions of the same list of JSON rows and get exactly what changed. Hand it yesterday's price list and today's, last week's product feed and this week's, or two exports of the same CRM, name the field that identifies a row, and it tells you which rows were added, removed or changed, down to which fields moved on each one.
Built for AI agents. No install, no API key, no signup. Connect by URL and call it.
https://dataset-diff-detector.nerolabs.workers.dev/mcpFree to use while in early access.
What it does
One call compares a before snapshot (oldRows) with an after snapshot (newRows):
- Matches rows across the two sides on keyFields, such as sku, id or email (one field or several). Without a key it matches on full row content, so an edited row shows as one removed row plus one added row.
- Compares every field on each matched pair, minus any ignoreFields (timestamps that always differ), or only the compareFields you name.
- Returns one row per difference with its status, key, oldValues, newValues and changedFields, plus a summary counting added, removed, changed and unchanged rows. Turn on includeUnchanged to get the unchanged rows back too.
Comparison is exact, so nothing is quietly glossed over: "24.99" as text and 24.99 as a number count as a change, as do "Blue" and "blue ", and null becoming a value. Nested objects compare by value, whatever order their keys are in.
It is honest about messy input. The summary warns when a key value appears twice on one side (the last row is kept and the count is reported), when rows have no key field at all, and when a field you named appears in no row, which is usually a typo.
Tools
Connect
Claude Code
claude mcp add --transport http dataset-diff-detector https://dataset-diff-detector.nerolabs.workers.dev/mcpClaude Desktop / claude.ai: Settings, Connectors, Add custom connector, paste the URL above.
Cursor, Windsurf, VS Code and other MCP clients
{
"mcpServers": {
"dataset-diff-detector": {
"url": "https://dataset-diff-detector.nerolabs.workers.dev/mcp"
}
}
}Example
Yesterday's and today's price list go in, with the scrape timestamp ignored:
{
"oldRows": [
{"sku": "A100", "title": "Blue Widget", "price": 19.99, "stock": 42, "scrapedAt": "2026-09-11T08:00:00Z"},
{"sku": "A101", "title": "Red Widget", "price": "24.99", "stock": 0, "scrapedAt": "2026-09-11T08:00:00Z"},
{"sku": "A102", "title": "Green Widget", "price": 15.5, "stock": 8, "scrapedAt": "2026-09-11T08:00:00Z"},
{"sku": "A104", "title": "Purple Widget", "price": 9.99, "discount": null, "scrapedAt": "2026-09-11T08:00:00Z"},
{"sku": "A105", "title": "Orange Widget", "price": 30, "stock": 3, "scrapedAt": "2026-09-11T08:00:00Z"}
],
"newRows": [
{"sku": "A100", "title": "Blue Widget", "price": 17.99, "stock": 30, "scrapedAt": "2026-09-12T08:00:00Z"},
{"sku": "A101", "title": "Red Widget", "price": 24.99, "stock": 0, "scrapedAt": "2026-09-12T08:00:00Z"},
{"sku": "A102", "title": "Green Widget", "price": 15.5, "stock": 8, "scrapedAt": "2026-09-12T08:00:00Z"},
{"sku": "A104", "title": "Purple Widget", "price": 9.99, "discount": 0.1, "scrapedAt": "2026-09-12T08:00:00Z"},
{"sku": "A106", "title": "Yellow Widget", "price": 12, "stock": 100, "scrapedAt": "2026-09-12T08:00:00Z"}
],
"keyFields": ["sku"],
"ignoreFields": ["sShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-09-19restoreB → Ascore 88
Dataset Diff & Change Detector: common questions
- Is Dataset Diff & Change Detector MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Dataset Diff & Change Detector safety report
- How do I install Dataset Diff & Change Detector?
- It runs remotely at dataset-diff-detector.nerolabs.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Dataset Diff & Change Detector need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Dataset Diff & Change Detector maintained?
- The last commit was 52 days ago (2026-09-13). The latest release is v0.1.0.
- Is Dataset Diff & Change Detector up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Dataset Diff & Change Detector compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.