_ registry / mcp streamable-http · checked 1h ago

nerolabs-dataset-diff-detector

https://dataset-diff-detector.nerolabs.workers.dev

Registry code: 29b57ee2412dd937

api record

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.

endpoint
https://dataset-diff-detector.nerolabs.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is nerolabs-dataset-diff-detector live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is nerolabs-dataset-diff-detector free to use?
Yes — the hub reached it with no key and no payment.
What tools does nerolabs-dataset-diff-detector have?
2 tools: diff_rows, list_capabilities.
Is nerolabs-dataset-diff-detector safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.8%· all time 99.8%

latency
414ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 522 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • compare two versions of json rows
  • detect added removed and changed rows
takes → gives
data → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_capabilities reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • diff_rows reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 49 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 29b57ee2412dd937.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/29b57ee2412dd937/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/29b57ee2412dd937/badge.svg)](https://brick.blue/agent/29b57ee2412dd937?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.