Home / MCP registry index / earth.terramcp/terramcp
TerraMCP
earth.terramcp/terramcp in the official MCP registry.
Endpoint https://terramcp.earth/mcp.
The registry describes it as: A Wrench AI service for environmental source discovery and live UK open-data tools.
We read its 33 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
search_sources get_source list_categories top_sources get_consultant nrw_stations nrw_measures nrw_readings os_names ea_groundwater_stations ea_flood_features ne_designated_sites wq_sampling_points wq_measurements sepa_stations sepa_series sepa_values bgs_collections bgs_features planning_entities flood_zone_at_point tide_stations tide_readings rainfall_stations rainfall_latest flood_find_stations flood_get_readings flood_list_warnings ea_hydro_series nrfa_station_info nrfa_get_timeseries usgs_daily dem_clip
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/earth-terramcp-terramcp)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.