Home / MCP registry index / io.github.eduair94/cambio-uruguay
Cambio Uruguay
io.github.eduair94/cambio-uruguay in the official MCP registry.
Endpoint https://mcp.cambio-uruguay.com/mcp. Source: github.com/eduair94/cambio-uruguay.git.
The registry describes it as: Uruguay: exchange rates, rentals, used cars, product prices and search across cambio-uruguay.com
We read its 29 tools on 2026-10-27. 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
get_rates best_house convert list_houses get_evolution get_news daily_summary geocode_uy_address search_rentals rank_rentals_for_household get_rental rental_market_stats estimate_fair_rent compare_neighborhoods find_property_opportunities search_used_cars find_car_opportunities get_car car_model_prices car_declared_risks car_market_report list_directories search_products plan_home_setup check_online_store supermarket_prices search_site read_page site_sections
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-eduair94-cambio-uruguay)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.