protogrid

Search / io.github.aidatatools-dev/data-quality-gate

Data Quality Gate - deterministic post-scrape cleaner + verdict

R0· no sign-in

Post-scrape data cleaner, no LLM: repairs mojibake, HTML, invisible chars. Plus a verdict.

v0.3.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality80good
Trust77of 100
Uptime, 30 days100%
Latency p50341 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "data-quality-gate": {
      "type": "http",
      "url": "https://www.aidatatools.dev/api/mcp_server"
    }
  }
}
claude mcp add --transport http data-quality-gate https://www.aidatatools.dev/api/mcp_server
[mcp_servers.data-quality-gate]
url = "https://www.aidatatools.dev/api/mcp_server"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "data-quality-gate": {
      "type": "remote",
      "url": "https://www.aidatatools.dev/api/mcp_server",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "data-quality-gate": {
      "type": "http",
      "url": "https://www.aidatatools.dev/api/mcp_server"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=data-quality-gate&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LmFpZGF0YXRvb2xzLmRldi9hcGkvbWNwX3NlcnZlciJ9"
}
{
  "servers": {
    "data-quality-gate": {
      "type": "http",
      "url": "https://www.aidatatools.dev/api/mcp_server"
    }
  }
}
{
  "mcpServers": {
    "data-quality-gate": {
      "httpUrl": "https://www.aidatatools.dev/api/mcp_server"
    }
  }
}
extensions:
  "data-quality-gate":
    enabled: true
    name: "data-quality-gate"
    type: streamable_http
    uri: "https://www.aidatatools.dev/api/mcp_server"
    timeout: 300

Quality 80 / 100good

protocol88 · weight 25
  • pass
    protocol.modernsupports 2026-07-28 (server/discover)
  • pass
    protocol.statelessanswers without a session
  • pass
    protocol.transportstreamable HTTP
  • warn
    protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene64 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length2 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_dataset_quality (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); clean_scraped_data (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); clean_scraped_data_audited (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 1,927 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 1,927 tokens to load them all · tool set 2690ec8bfd9b · checked 2026-10-19 10:20 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 77 / 100

no-repository
provenance45
liveness100
freshness85
hygiene80

+website +reachable +uptime-100% ~updated-68d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://www.aidatatools.dev/api/mcp_server streamable-httpnoneyes100%341 ms2026-07-282026-10-19

Tools (3)

check_dataset_qualityCall this before using any dataset. Returns a deterministic quality verdict (RELIABLE / USABLE_WITH_CLEANING / UNRELIABLE) with exact facts: completeness, nulls, type consistency, impossible values, duplicates, outliers, and (on financial/trading data) cross-source price divergence. 100% deterministic, no LLM. Free -- this MCP endpoint runs the engine directly; POST /api (plain REST, same engine) is x402-gated at $0.01/call instead. Input: rawJson (a JSON array of row objects, or a single object); datasetId is accepted but not resolvable on this deployment -- pass rawJson instead.
clean_scraped_dataPAID TIER, CALLED FROM A FREE ENDPOINT -- READ THIS FIRST: this tool does NOT return your cleaned data, and its response has NO `data` key. It returns {"status": "payment_required", "what_we_found_in_your_data": {...}, "get_the_repaired_data": {...}}. Do not treat its output as cleaned data and do not write it back into your dataset. WHAT YOU GET HERE, FREE: an exact inventory of the defects in YOUR data -- which repair rules would fire, how many values each would change, and which cases cannot be repaired safely and need your decision. HOW TO GET THE REPAIRED DATA: make the one call named in `get_the_repaired_data` -- POST https://www.aidatatools.dev/api/clean, $0.04 via x402, no account, no API key, no signup. That response body IS the cleaned dataset, in the shape you posted it. WHY THE SPLIT: detection is free on this endpoint and always has been (check_dataset_quality reports the same defects). The repaired artifact is the paid product, because it is re-bought on every extraction run rather than cached like a verdict. WHAT THE PAID CALL DOES: removes leftover HTML tags and entities, decodes mojibake ('Café' -> 'Café'), strips invisible characters (zero-width, BOM, soft hyphen), normalises non-breaking spaces and trims values -- across nested objects and arrays too. 100% deterministic, no LLM: the same input always yields byte-identical output, and cleaning twice equals cleaning once. It repairs how data was ENCODED, never what it SAYS: masked placeholders ('N/A', 'None'), near-duplicate rows and failed extractions ('access denied', 'captcha', which mean that record must be re-scraped) are reported with a proposal, never silently deleted or rewritten. The full boundary -- 7 rules applied automatically, 5 needing an explicit opt-in, 8 only ever reported -- is at GET https://www.aidatatools.dev/api/clean.
clean_scraped_data_auditedPAID TIER, CALLED FROM A FREE ENDPOINT -- READ THIS FIRST: this tool does NOT return your cleaned data, and its response has NO `data` key. It returns {"status": "payment_required", "what_we_found_in_your_data": {...}, "get_the_repaired_data": {...}}. Do not treat its output as cleaned data and do not write it back into your dataset. WHAT YOU GET HERE, FREE: an exact inventory of the defects in YOUR data -- which repair rules would fire, how many values each would change, and which cases cannot be repaired safely and need your decision. HOW TO GET THE REPAIRED DATA: make the one call named in `get_the_repaired_data` -- POST https://www.aidatatools.dev/api/clean/audit, $0.12 via x402, no account, no API key, no signup. That response body IS the cleaned dataset, in the shape you posted it. WHY THE SPLIT: detection is free on this endpoint and always has been (check_dataset_quality reports the same defects). The repaired artifact is the paid product, because it is re-bought on every extraction run rather than cached like a verdict. WHAT THE PAID CALL DOES: the same repair as clean_scraped_data, plus a complete audit trail: every transformation with its path, rule, before and after value, a replay_id, and input/output SHA-256. The ledger is a full inverse patch -- applying it in reverse reconstructs your original input byte for byte. Use it when you must be able to PROVE later what changed and why.

Schemas: list_tools.

Similar MCP servers

More from io.github.aidatatools-dev

Official server.json
{
  "name": "io.github.aidatatools-dev/data-quality-gate",
  "_meta": {
    "io.modelcontextprotocol.registry/publisher-provided": {
      "docs": {
        "full": "https://www.aidatatools.dev/llms-full.txt",
        "openapi": "https://www.aidatatools.dev/openapi.json",
        "summary": "https://www.aidatatools.dev/llms.txt",
        "boundary": "https://www.aidatatools.dev/api/clean"
      },
      "tags": [
        "data cleaning",
        "scraping repair",
        "post-scrape sanitization",
        "deterministic data repair",
        "mojibake correction",
        "encoding repair",
        "scraper output cleaning",
        "auditable data repair"
      ],
      "tools": {
        "clean_scraped_data": "Free to call, but it does NOT return the repaired data -- its response has no 'data' key. It reports which rules would fire on your data and what needs your decision, then names the paid call that hands the data back: POST https://www.aidatatools.dev/api/clean, $0.04 via x402, no account or signup. Call it after every extraction run -- a verdict is cached per source, but dirt is produced fresh by every run.",
        "check_dataset_quality": "FREE here. The full quality verdict: score, per-check facts, and RELIABLE / USABLE_WITH_CLEANING / UNRELIABLE. Bought once per source, then cached.",
        "clean_scraped_data_audited": "Same, pointing at POST https://www.aidatatools.dev/api/clean/audit, $0.12: the repaired data plus a replayable, reversible ledger of every transformation."
      },
      "boundary": "20 rules, published in full and free at GET https://www.aidatatools.dev/api/clean -- readable before paying. 7 are applied automatically (information-preserving), 5 need an explicit opt-in (they change row count, type or schema), and 8 are only ever reported, with no option to turn them on: near-duplicates are never merged, ambiguous placeholders are never nulled ('None' is a surname, 'NA' is Namibia), full NFKC is never applied (it rewrites 10^2 to 102), and failed extractions ('captcha', 'access denied') are never deleted -- that value is what tells you the record must be re-scraped. Impossible values are never repaired at all.",
      "measured": "Real 100-row Amazon scrape, 57,956 nested string values: 453 repairs, 0 reverts, 0 values emptied. A control set of legitimate-but-suspicious data (French accents, Persian ZWNJ, emoji ZWJ, 10^2, AT&T, surname 'None', 'NA') comes back byte-for-byte identical: 0 changes, 11 flags.",
      "guarantees": "Deterministic and idempotent. No value is emptied, retyped or reordered by an automatic rule. A repair that would introduce a defect the original did not have is reverted and flagged. The audited tier's ledger restores the input byte for byte.",
      "positioning": "Deterministic post-scrape data cleaner and quality gate. Repairs how data was ENCODED -- residual HTML, mojibake ('Café' -> 'Café'), invisible characters, non-breaking spaces -- and never what it SAYS. No LLM: identical input always yields byte-identical output, so results can be cached, replayed and audited.",
      "why_repair_is_paid": "Detection is free on this endpoint and always has been. The repaired artifact is the paid product, because it is re-bought on every extraction run rather than cached like a verdict. Both cleaning tools say so in their own descriptions, before they are called."
    }
  },
  "title": "Data Quality Gate - deterministic post-scrape cleaner + verdict",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://www.aidatatools.dev/api/mcp_server",
      "type": "streamable-http"
    }
  ],
  "version": "0.3.0",
  "websiteUrl": "https://www.aidatatools.dev/llms.txt",
  "description": "Post-scrape data cleaner, no LLM: repairs mojibake, HTML, invisible chars. Plus a verdict."
}