icedq-mcp vs com.dropwatchhq/ehr-migration-checklist
icedq-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
icedq-mcp is a plugin bundle for AI coding tools published by iceDQ Integration Team. No marketplace we read lists it any more. com.dropwatchhq/ehr-migration-checklist is an MCP server published by dropwatchhq.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace icedq-tools/mcp-server | Removed on 2026-10-15 Version: 2.0.3 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | icedq-mcpno longer listed · | com.dropwatchhq/ehr-migration-checklist |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@icedq/mcp-server) | Not stated |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 13, secrets among them: 4 | Not published |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/icedq-tools/mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of icedq-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
DQX by Databricks Labs — AI assistant skills for defining, applying, storing, and profiling data quality rules in PySpark.
-
Add checks and metrics to dlt pipelines — inspect schema for candidates, define column-level validations and load metrics, run them on every pipeline load, and review results with…
-
Data validation and quality assurance tools using Pydantic v2, schema validation, data contracts, and quality monitoring for PlanetScale PostgreSQL databases
-
Audit datasets for completeness, consistency, accuracy, and validity. 3 stdlib-only Python tools: data profiler with DQS scoring, missing value analyzer with MCAR/MAR/MNAR…
-
SQL data health analyzer and pipeline observability evaluator.
-
Auto-discover validation rules from data — scan, profile, health-score. No rules to write.
What each says it does
icedq-mcp
Author, run, and schedule iceDQ data quality rules, bundled with the iceDQ MCP server.
com.dropwatchhq/ehr-migration-checklist
EHR-migration data-integrity checklist: silent data-loss modes anchored to HL7/FHIR, USCDI, HIPAA.
How to run each
icedq-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.dropwatchhq/ehr-migration-checklist
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of com.dropwatchhq/ehr-migration-checklist publish no settings it asks for, so we do not compare settings.
What it can do: icedq-mcp · What it can do: com.dropwatchhq/ehr-migration-checklist · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.