Home / MCP registry index / io.github.Aryan-Jhaveri/mcp-statcan
Statistics Canada MCP Server
io.github.Aryan-Jhaveri/mcp-statcan in the official MCP registry.
Endpoint https://mcp-statcan.com/mcp. Source: github.com/Aryan-Jhaveri/mcp-statcan.
The registry describes it as: Access Statistics Canada data via the Web Data Services API
We read its 17 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_code_sets get_all_cubes_list get_all_cubes_list_lite search_cubes_by_title get_cube_metadata get_changed_series_data_from_cube_pid_coord get_series_info get_changed_cube_list get_series_info_from_vector get_bulk_vector_data_by_range get_changed_series_data_from_vector get_changed_series_list get_sdmx_structure get_sdmx_data query_sdmx get_sdmx_vector_data get_sdmx_key_for_dimension
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-aryan-jhaveri-mcp-statcan)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.