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.
      4 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
      38 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
      47 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

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: plan_query orchestrates multi-source questions, search_tools discovers tools, and call_tool executes them. However, plan_query also returns tools to call, which could overlap with search_tools for simple discovery, creating minor ambiguity.

    Naming Consistency5/5

    All names use snake_case and follow a consistent verb_noun pattern (call_tool, search_tools, plan_query), making them predictable and readable.

    Tool Count5/5

    With only 3 tools, the server is minimal but appropriate for a meta-orchestration layer; each tool (plan, search, call) is essential to the workflow, and no tool feels redundant.

    Completeness4/5

    The surface covers the core lifecycle of planning, discovering, and executing tools. A direct 'list all tools' operation is missing, but search_tools with a broad query can substitute, so there's no hard dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources