nerolabs-dataset-join-merge

endpoint

https://dataset-join-merge.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 nerolabs-dataset-join-merge 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-join-merge free to use?

Yes — the hub reached it with no key and no payment.

What tools does nerolabs-dataset-join-merge have?

2 tools: join_rows, list_capabilities.

Is nerolabs-dataset-join-merge 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.

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 13h ago

  Returns every join type, key matching mode, conflict strategy and fan-out mode this server supports, the fields it adds to each row, and the input and output row limits per call. Free, processes no data.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• join_rows reads unknown never probed

  Joins two lists of JSON rows on a shared key, like a SQL join or a spreadsheet VLOOKUP, and returns the combined rows plus a summary: how many rows matched on each side, match rates, and warnings for duplicate keys, rows missing the key and key fields that exist on no row. Use it to enrich a list with fields from a lookup table (left join), keep only the overlap (inner), combine two sources into one table (full), find rows in one list that are missing from the other (leftAnti or rightAnti), or stack two same-shape lists (union). Keys match case-insensitively with whitespace trimmed by default, and the key can have a different name on each side (email on the left, contact_email on the right). Input and output rows are capped per call; a many-to-many join that would exceed the output cap is refused with the predicted row count, never truncated. Call list_capabilities for the exact limits.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091

  {
    "type": "object",
    "required": [
      "leftRows",
      "rightRows"
    ],
    "properties": {
      "joinType": {
        "enum": [
          "left",
          "inner",
          "right",
          "full",
          "leftAnti",
          "rightAnti",
          "union"
        ],
        "type": "string",
        "description": "Which rows to keep. left (default): every left row, enriched where a match exists. inner: matched rows only. right: every right row. full: everything from both sides. leftAnti: left rows with no match on the right. rightAnti: right rows with no match on the left. union: stack both lists, no key needed."
      },
      "leftRows": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "The LEFT table: the main rows you want to keep or enrich. Each row is a JSON object; keys may differ between rows."
      },
      "rightRows": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "The RIGHT table: the lookup rows to pull matching fields from. Each row is a JSON object."
      },
      "keyMatching": {
        "enum": [
          "normalized",
          "exact"
        ],
        "type": "string",
        "description": "normalized (default): case-insensitive, trimmed, repeated spaces collapsed, 123 matches \"123\". exact: values must be identical."
      },
      "rightFields": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Only copy these fields from the matching right row, like choosing VLOOKUP return columns. Leave out to copy every right field."
      },
      "leftKeyFields": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "The field name(s) on the left rows to match on, for example [\"email\"], or [\"firstName\",\"lastName\"] for a composite key. Required for every joinType except union."
      },
      "rightKeyFields": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "The matching field name(s) on the right rows, in the same order as leftKeyFields, for example [\"contact_email\"]. Leave out when the right rows use the same names as the left."
      },
      "includeJoinInfo": {
        "type": "boolean",
        "description": "On by default: every row gets _joinStatus (\"matched\", \"left_only\", \"right_only\") and _matchCount. Set false for rows with only your own fields."
      },
      "multipleMatches": {
        "enum": [
          "all",
          "first"
        ],
        "type": "string",
        "description": "When one key matches several right rows. all (default): one output row per matching pair, like SQL. first: only the first matching right row, like VLOOKUP, so each left row appears once."
      },
      "onFieldConflict": {
        "enum": [
          "prefixRight",
          "keepLeft",
          "keepRight"
        ],
        "type": "string",
        "description": "When a right field has the same name as a left field. prefixRight (default): keep both, the right one renamed with rightFieldPrefix. keepLeft: ignore the right value. keepRight: overwrite the left value."
      },
      "rightFieldPrefix": {
        "type": "string",
        "description": "Prefix for conflicting right fields when onFieldConflict is prefixRight. Default \"right_\", so price becomes right_price."
      }
    },
    "additionalProperties": false
  }

  arguments 91 lines copy

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

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.