metric-shift-mcp-server
Related Servers
Alternatives to metric-shift-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables comprehensive analysis of CSV files and SQLite databases through tools for statistics, correlations, anomaly detection, pivot tables, time series analysis, visualization, and automated insights discovery.16-
- AlicenseBqualityBmaintenanceStatistical analysis, forecasting, and ML for business data (Shopify, Stripe, WooCommerce, eBay, GA4, Search Console). Upload a CSV or connect live data sources — ask a question in Claude or Cursor, get an interactive HTML report192 npm7MIT
- AlicenseBqualityFmaintenanceEnables autonomous data exploration on .csv-based datasets, providing intelligent insights with minimal effort.2544MIT
- FlicenseNot gradedqualityCmaintenanceSales anomaly detection for a sample café dataset. Enables analyzing weekly sales, product history, and detecting anomalies like closures or pricing glitches.-
- AlicenseAqualityBmaintenanceSuperhuman data-driven science. Allows agents to upload any tabular dataset, specify a target column, and get validated predictive patterns (with p-values, effect sizes, and context from literature) that surface feature interactions and subgroup effects you'd otherwise miss. Many discoveries already made, free for open data!147MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to analyze large CSV files locally by importing them into SQLite, profiling columns, and running read-only SQL queries without data leaving the machine.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one inspects data to provide context (columns, date ranges, candidates), while the other performs the actual shift localization. There is no overlap or ambiguity between them.
Both tools follow the exact same verb_noun pattern with a consistent prefix 'metric_shift_'. The names clearly indicate action (inspect/localize) and domain, making them predictable and easy to navigate.
With only 2 tools, the server feels slightly thin but is well-scoped for a narrow, specialized purpose: metric shift analysis. The two tools cover the entire intended workflow (inspect then localize), so the count is appropriate for the niche.
The tool surface covers the essential workflow: inspection before localization, which is explicitly recommended. Minor gaps exist (e.g., no tool for comparing periods or exporting results), but for the stated purpose of answering 'where did the metric drop?', the coverage is sufficient.