ML Booster Map
Related Servers
Alternatives to ML Booster Map
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that unifies official Turkish open data sources into a single interface, letting AI agents query and compare normalized indicators like population, inflation, and GDP through natural language.10MIT
- AlicenseAqualityDmaintenanceEnables querying Turkish economic data (inflation, FX rates, policy rates, etc.) from TCMB EVDS via curated tools, preventing LLM hallucination.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access official statistical and economic indicator datasets from Eurostat, World Bank, OECD, IMF, WHO, and national statistical offices across 150+ countries through natural-language dataset discovery, inspection, time-series retrieval, SQL queries, CSV export, and account/watchlist management.MIT
- AlicenseAqualityDmaintenanceProvides unified access to Turkish official data from TÜİK (statistics via SDMX) and TCMB EVDS (financial series), enabling search, query, and tidy CSV export with full frequency, aggregation, and formula support.161MIT
- AlicenseAqualityBmaintenanceEnables querying Malaysian official statistics through natural language, with correct series resolution, statistical transformations, and provenance-attached data.11MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to query Turkey's public data, including central-bank FX rates, earthquake catalog, weather forecasts, public holidays, and offline validation of Turkish ID, tax, and IBAN numbers, with sourced and timestamped responses.4485 npm1MIT
TDQS
Scored across 7 tools
Most tools have clearly distinct roles: list_sectors/list_sources are catalog reads, show_map renders a sector map, discover_series finds series, fetch_series ingests them, build_panel assembles the panel, and health runs canaries. The only mild overlaps are list_sources vs. show_map (both surface sources for a sector) and discover_series's catalog-seed mode vs. list_sources, but the descriptions differentiate them adequately.
Six of seven tools follow a clean snake_case verb_noun pattern (build_panel, list_sources, show_map, discover_series, fetch_series, list_sectors). The lone outlier is 'health', a bare noun that breaks the pattern but is still unambiguous.
Seven tools is well within the sweet spot and each maps to a distinct stage of the workflow: catalog inspection, discovery, ingestion, panel building, and validation. No tool feels redundant or padded.
The core discover → fetch → build_panel pipeline plus health checks is covered, but there is no way to inspect the local silver layer or list previously built panels, and no update/delete or cleanup operations. Agents can work around this via returned paths/summaries, but the lifecycle surface has notable gaps.