MapleStats MCP
Related Servers
Alternatives to MapleStats MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceGives AI agents structured, bilingual access to Canadian federal, provincial, and municipal open-data APIs, covering exchange rates, statistics, weather, recalls, drugs, immigration, parliamentary data, geospatial datasets, and local SQLite persistence. It also provides discovery and orchestration tools for searching, planning, and executing cross-API queries.MIT
- AlicenseNot gradedqualityFmaintenanceProvides access to Statistics Canada official statistics without authentication, enabling AI agents to query Canadian economic and demographic data.4 npmMIT
- AlicenseAqualityCmaintenanceMCP server giving LLMs live access to Statistics Canada's full catalogue of 8,200+ data tables via the Web Data Service, with tools to search tables, inspect dimensions, and fetch time series data using plain-language prompts.5MIT
- AlicenseAqualityDmaintenanceMCP server serving official statistics from major data agencies (Statistics Canada, FRED, BLS, World Bank, etc.) as tools with provenance and verification, enabling search, retrieval, analysis, and monitoring via natural language.1158 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search, explore, and analyze Québec open data (Données Québec, Ville de Montréal, IGO) via natural language, including SQL queries, geocoding, and spatial operations.1MIT
- AlicenseAqualityDmaintenanceProvides LLM agents with live access to Canadian economic and financial data (exchange rates, interest rates, inflation, etc.) through the Bank of Canada Valet API, with no API key required.105MIT
TDQS
Scored across 3 tools
The three tools have distinct roles: discovery (search_tools), multi-source planning (plan_query), and execution (call_tool). The only overlap is that search_tools and plan_query both surface tools, but the descriptions explicitly draw the boundary (single narrow need vs. cross-source or unknown start), so misselection is unlikely though not impossible.
All three names follow a consistent verb_noun snake_case pattern: search_tools, plan_query, call_tool. The verbs are clear and the nouns map directly to each tool's function.
Three tools is exactly right for a gateway/meta-server whose catalogue is reached through call_tool. Each tool earns its place: one to discover, one to plan, one to execute.
The lifecycle of find -> plan -> execute is fully covered, including error handling and detail levels. The main minor gap is the absence of a browse/list-all-catalogue operation, so agents must rely on search queries to discover what exists.