Home / MCP registry index / com.rentalanalytics/rent-tools
RentalAnalytics rent tools
com.rentalanalytics/rent-tools in the official MCP registry.
Endpoint https://rentalanalytics.com/mcp. Source: github.com/CGABrew7/rentalanalytics.
The registry describes it as: Read-only HUD rent lookup and the site's existing rental calculators.
We read its 16 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
lookup_hud_rent estimate_rent calculate_cap_rate calculate_cash_flow calculate_dscr calculate_amortization compare_str_ltr advise_lease_renewal lookup_covered_market calculate_opex lookup_rent_to_income lookup_gross_yield calculate_gross_yield illustrate_1031_exchange illustrate_cost_segregation lookup_city_rules
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-rentalanalytics-rent-tools)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.