Skip to main content
Glama
dsanchezp18

MapleStats MCP

by dsanchezp18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MapleStats MCP

No user-submitted related servers found.

    Related Servers

    • mcp-statscan

      pipeworx-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides access to Statistics Canada official statistics without authentication, enabling AI agents to query Canadian economic and demographic data.
      1 npm
      MIT

    • statcan-mcp

      arose26
      A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      5
      21 npm
      MIT

    • starwell-mcp

      Adarsh4052
      A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      11
      37 npm
      MIT

    • boc-valet-mcp

      Chatusvi-Karnati
      A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools occupy distinct roles: plan_query for multi-source research planning, search_tools for locating a single tool, call_tool for execution. The descriptions explicitly cross-reference each other with 'use X instead' guidance, though plan_query and search_tools both serve discovery and could occasionally be confused by an agent unsure of question scope.

    Naming Consistency5/5

    All three tools follow a clean verb_noun snake_case pattern (plan_query, search_tools, call_tool) with no mixing of conventions or vague verbs. The naming is fully predictable and readable.

    Tool Count4/5

    Three tools is at the low end but well-matched to a router/meta-layer server whose real data tools are discovered dynamically rather than enumerated as fixed tools. The plan-search-execute trio is coherent and each earns its place, though the surface is minimal.

    Completeness4/5

    The meta-lifecycle is covered: planning (plan_query), discovery (search_tools), and execution (call_tool), plus error handling and provenance described. The main gap is no dedicated catalogue-browsing tool, relying on search_tools and the implied list_tools, which could hinder full-surface exploration.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources