Koskamo

Dataset Diff & Change Detector MCP

A remote MCP server that allows agents to compare two versions of a list of JSON rows. It identifies exactly which rows were added, removed, or changed between the two datasets, supporting up to 500 rows per call via the diff_rows tool.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Dataset Diff & Change Detector MCP logo, by Nero LabsCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Nero Labs
MCP endpoint (Streamable HTTP)
https://dataset-diff-detector.nerolabs.workers.dev/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Compare two versions of a JSON row list
  • Identify added, removed, or changed fields
  • Check dataset integrity between versions

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
nerolabs-dataset-diff-detector 0.1.0
MCP protocol negotiated in check
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Call diff_rows with the before rows (oldRows), the after rows (newRows) and the field that identifies a row (keyFields, for example ["sku"]). Call list_capabilities first if you need the exact comparison rules or the row limit.

Tools

2 advertised

list_capabilities
Advertised by the server during the last successful anonymous check.

Returns 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.

list_capabilities input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
diff_rows
Advertised by the server during the last successful anonymous check.

Compares 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.

diff_rows input schema
{
  "type": "object",
  "required": [
    "oldRows",
    "newRows"
  ],
  "properties": {
    "newRows": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "The after snapshot: a JSON array of row objects, the same kind of rows as oldRows. At least one row."
    },
    "oldRows": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "The before snapshot: a JSON array of row objects. At least one row. Keys may differ between rows."
    },
    "keyFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Field name(s) that uniquely identify a row on both sides, for example [\"sku\"] or [\"country\",\"sku\"]. Strongly recommended: without it a changed row is reported as one removed row plus one added row."
    },
    "ignoreFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional. Fields never compared, for example [\"scrapedAt\",\"lastChecked\"], so a timestamp alone does not mark a row changed."
    },
    "compareFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional. Only these fields decide whether a matched row changed. Default: every field on either row."
    },
    "includeUnchanged": {
      "type": "boolean",
      "description": "Optional, default false. Set true to also return matched rows with no difference (status \"unchanged\"). They are always counted in the summary."
    }
  },
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
723 ms
95th percentile latency
723 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 723 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http dataset-diff-change-detector-mcp https://dataset-diff-detector.nerolabs.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add dataset-diff-change-detector-mcp --url https://dataset-diff-detector.nerolabs.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable dataset-diff-change-detector-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "dataset-diff-change-detector-mcp": {
      "url": "https://dataset-diff-detector.nerolabs.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "dataset-diff-change-detector-mcp": {
      "type": "streamableHttp",
      "url": "https://dataset-diff-detector.nerolabs.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start dataset-diff-change-detector-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "dataset-diff-change-detector-mcp": {
      "type": "http",
      "url": "https://dataset-diff-detector.nerolabs.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http dataset-diff-change-detector-mcp https://dataset-diff-detector.nerolabs.workers.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://dataset-diff-detector.nerolabs.workers.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "dataset-diff-change-detector-mcp": {
      "serverUrl": "https://dataset-diff-detector.nerolabs.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Dataset Diff & Change Detector MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.