Home / MCP registry index / io.github.rpconroy/gdex-mcp
io.github.rpconroy/gdex-mcp
io.github.rpconroy/gdex-mcp in the official MCP registry.
Endpoint https://gdex-mcp.k8s.ucar.edu/mcp. Source: github.com/NCAR/gdex-mcp.
The registry describes it as: MCP server for the GDEX (Geoscience Data Exchange) data portal: datasets, files, metrics, subsetting
We read its 30 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
list_datasets get_dataset_metadata get_dataset_field describe_dataset get_file_groups get_dataset_files find_dataset_files get_filesearch_datatypes get_filesearch_grid_filters get_filesearch_cyclone_fix_filters get_filesearch_sensor_filters get_filesearch_grid_files get_filesearch_cyclone_fix_files get_filesearch_sensor_files get_filesearch_result_page get_data_access has_arco get_arco_variables search_arco_variables get_portal_metrics get_dataset_metrics get_staff list_request_statuses check_request_status get_request_files get_control_file_template validate_subset_request submit_subset_request submit_and_wait_for_request purge_request
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-rpconroy-gdex-mcp)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.