DataClinic MCP
Related Servers
Alternatives to DataClinic MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to discover local CSV and Parquet datasets, inspect schemas, profile columns, detect missing values and duplicate records, and run capped read-only SQL analytics.MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLM clients to load, clean, visualize, and analyze tabular datasets, and to generate multi-format analytic reports through natural language instructions.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to validate CSV exports against schemas, infer schemas from example files, profile datasets, and diff before/after exports for lab/LIMS data-quality checks.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to audit dbt project quality, profile warehouse data, detect schema drift, and safely generate or update model documentation and tests through natural language.-
- AlicenseNot gradedqualityBmaintenanceIt enables AI assistants to audit CSV and Excel files for empty data, missing or null values, and duplicate rows, and to verify SQLite or PostgreSQL table existence and column structure before loading data.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to audit dbt project quality, profile warehouse data, detect schema drift, and auto-generate or update documentation and tests through natural language.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one loads new data into the session, the other manages existing session sources. There is no overlap or ambiguity between them.
Both tool names use a verb_noun pattern (load_dataset, manage_sources), which is consistent. The slight deviation is that 'manage_sources' is broader than a single action, but the pattern is still predictable.
With only two tools, the server feels very thin for a data-clinic purpose. A data analysis server would typically need at least a few more operations (e.g., inspect, transform, summarize) to be useful, so the count is too low for the apparent scope.
The server covers loading data and managing sources, but lacks any analysis, transformation, or export operations. The domain is data handling, and the surface is severely incomplete for a 'DataClinic'—agents can load data but cannot do anything with it beyond listing/closing sources.