Home / MCP registry index / io.github.cyanheads/nasa-power-mcp-server
Nasa Power
io.github.cyanheads/nasa-power-mcp-server in the official MCP registry.
Endpoint https://nasa-power.caseyjhand.com/mcp. Source: github.com/cyanheads/nasa-power-mcp-server.
The registry describes it as: Query NASA POWER solar, wind, building, and agroclimatology data.
On 2026-10-31 we read its 8 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
nasa_power_get_timeseries nasa_power_get_climatology nasa_power_get_region nasa_power_compare_locations nasa_power_search_parameters nasa_power_list_reference nasa_power_dataframe_describe nasa_power_dataframe_query
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/io-github-cyanheads-nasa-power-mcp-server)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.