edamcp
Related Servers
Alternatives to edamcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that provides data visualization and machine learning tools, featuring automated intent-based pipeline routing for data cleaning and model training. It enables LLMs to process CSV or JSON data to generate visual charts, perform regressions, or execute clustering analysis.16-
- AlicenseAqualityAmaintenanceMCP server that profiles local data files (CSV, Parquet, JSON, Excel) and returns compact structured summaries with data-quality flags, enabling AI agents to understand datasets without seeing raw rows.11MIT
- AlicenseAqualityDmaintenanceEnables exploratory data analysis through an MCP server, allowing AI assistants to load datasets, compute summary statistics, generate diagnostic plots, perform correlation analysis, and produce full markdown reports.6MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables the analysis of CSV and Parquet files by providing tools for statistical summaries, data previews, and structure exploration. It allows users to query local datasets and create sample data using natural language.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants the ability to connect to, query, profile, and monitor data sources — turning any LLM into an interactive data engineering copilot.MIT
- FlicenseAqualityDmaintenanceAn MCP server for dataset exploration and analysis, enabling LLM clients to perform summary, correlation, distribution, missing value analysis, data cleaning, and statistical tests directly on CSV files.3-
TDQS
Scored across 69 tools
Most tools have clearly distinct purposes, but auto_compare and compare_sources both perform schema diff + drift analysis and return a safe/risky/incompatible verdict, making them easy to confuse. A few other pairs (auto_quality vs. run_eda, plot_facet vs. plot_distribution) are related but descriptions clarify their roles.
The vast majority of tools follow a verb_noun pattern (check_*, clean_*, plot_*, auto_*, detect_*), but a few outliers like data_card, eda_storyboard, and profile break the pattern. The auto_* prefix also mixes verbs and nouns, but overall the conventions are largely consistent.
With 69 tools, the server is far beyond the typical 3-15 well-scoped range, and exceeds the 50+ extreme threshold. The sheer number forces agents to scan a massive list for every decision, hurting usability despite the broad feature set.
The tool surface covers the full data lifecycle: loading, exploring, profiling, quality checking, cleaning, plotting, comparison, reporting, and export. There are no obvious dead ends, and composite macros like auto_explore, auto_quality, and run_eda stitch the pieces together well.