# Dataparity (npm · dataparity)

Cross-database data diff and reconciliation for AI agents, with a portable row hash

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `dataparity`: 71/100 (this document), [markdown](https://verifymcp.io/servers/arif-js-dataparity/dataparity.md), [page](https://verifymcp.io/servers/arif-js-dataparity/dataparity)

## Channel facts

- Registry: `npm`
- Package: `dataparity`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 37 of 127 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 406 tokens (~81/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Dataparity MCP server?

Dataparity runs locally as an npm package, launched with npx -y dataparity. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add arif-js-dataparity -- npx -y dataparity
```

### Cursor

```json
{
  "mcpServers": {
    "arif-js-dataparity": {
      "command": "npx",
      "args": [
        "-y",
        "dataparity"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arif-js-dataparity": {
      "command": "npx",
      "args": [
        "-y",
        "dataparity"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add arif-js-dataparity -- npx -y dataparity
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arif-js-dataparity": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dataparity"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arif-js-dataparity --command npx --arg -y --arg dataparity
```

### Hermes

```yaml
mcp_servers:
  arif-js-dataparity:
    command: "npx"
    args: ["-y", "dataparity"]
```

### Netclaw

```json
{
  "McpServers": {
    "arif-js-dataparity": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dataparity"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add arif-js-dataparity -t stdio -c npx -a -y dataparity
```

### Other

```json
{
  "mcpServers": {
    "arif-js-dataparity": {
      "command": "npx",
      "args": [
        "-y",
        "dataparity"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 71, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 56)

First indexed and scored.

## MCP tools (4)

### `dataparity_list_sources` (~31 tokens)

List the configured data sources that can be diffed. Returns each source name, engine type and label.

### `dataparity_list_tables` (~61 tokens)

List the tables in a configured source, with their columns. Use this to find the right table and key columns before diffing.

Input parameters:

- `schema` (string): Optional schema to restrict the listing to.
- `source` (string, required): The configured source name.

### `dataparity_describe_table` (~61 tokens)

Describe one table: its columns, their types and whether they are nullable. Use this to choose key columns and comparison columns.

Input parameters:

- `source` (string, required): The configured source name.
- `table` (string, required): The table name, optionally schema-qualified.

### `dataparity_diff` (~238 tokens)

Compare two tables and report what changed. Works across different databases: both sides compute the same canonical row hash, so only hashes are compared, never raw data. Returns added, removed and modified rows, schema differences, a risk verdict, and the segments of data where the changes concentrate.

Input parameters:

- `columns` (array): Columns to compare. Defaults to every column the two tables share.
- `format` (string): Output format. Defaults to json.
- `key_columns` (array, required): Columns used to match rows across the two sides.
- `left` (string, required): The left source name.
- `left_table` (string, required): The table on the left.
- `max_attributions` (number): Maximum number of attribution segments to return. Defaults to 5.
- `max_changes` (number): Maximum number of row changes to return. Defaults to 100.
- `right` (string, required): The right source name.
- `right_table` (string, required): The table on the right.
- `sample` (boolean): Compare only a sample of rows. The result is marked as sampled.
- `where` (string): A WHERE expression applied to both sides.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/arif-js-dataparity/dataparity#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 56

## Common questions

### What is the Dataparity MCP server?

Dataparity is an MCP server listed in the public MCP registry as io.github.arif-js/dataparity. Cross-database data diff and reconciliation for AI agents, with a portable row hash. This page covers its npm package (dataparity).

### Is the Dataparity MCP server safe to use?

Dataparity scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Dataparity MCP server expose?

Dataparity exposes 4 tools: dataparity_list_sources, dataparity_list_tables, dataparity_describe_table, dataparity_diff. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.

### Is the Dataparity MCP server still maintained?

Dataparity is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Dataparity MCP server under?

Dataparity declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/dataparity
- Socket report: https://socket.dev/npm/package/dataparity
- Repository: https://github.com/arif-js/dataparity
- Changelog RSS feed: https://verifymcp.io/servers/arif-js-dataparity/dataparity.xml
- Changelog JSON feed: https://verifymcp.io/servers/arif-js-dataparity/dataparity.json
- HTML version of this page: https://verifymcp.io/servers/arif-js-dataparity/dataparity