com.lucidrents/building-intelligence
com.lucidrents/building-intelligence · 1.0.0
Building intelligence for NYC, LA, Chicago rentals: violations, 311, reviews, rents, landlords.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://lucidrents.com/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- lucidrents 1.0.0
- Handshake time
- 82 ms
- HTTP status
- 200
The tools it lists (5, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_buildingsSearch LucidRents for apartment buildings by address, building name, or partial address. Covers ~2M buildings in New York City, Los Angeles, and Chicago with public-record data: housing violations, 311 complaints, tenant reviews, rents, and building scores. Returns up to 10 matches with each building's slug (needed for get_building_report / get_review_summary) and its lucidrents.com report URL. Start here when the user gives an address.
get_building_reportFull report card for one building: LucidIQ score and letter grade, HPD/DOB violation counts, 311 complaint total, top violation categories (pests, heat, leaks, ...), review count and average rating, rent summary by bedroom count, rent stabilization, landlord name with their record URL, and 2-3 similar nearby buildings. Requires the building's slug — call search_buildings first if you only have an address. The returned url has the complete timeline, all reviews, and rent history; share it with the user.
get_landlord_recordPublic record for a landlord / property owner: portfolio size, total violations, 311 complaints, average building score across the portfolio, and worst building where available. Accepts either the owner name as it appears in a building report (e.g. "SMITH REALTY LLC") or a landlord page slug. The returned url lists every building they own with per-building records.
get_neighborhood_statsNeighborhood snapshot for a zip code: median asking rents by bedroom count and a 12-month crime summary (violent / property / quality-of-life, with year-over-year totals) sourced from the local police department. Use this for "what does rent cost in <area>" and "is <area> safe" questions. The returned url is the neighborhood page with building listings and trend charts.
get_review_summaryTenant review summary for one building: review count, average rating, 1-5 star distribution, and up to 3 recent pull quotes from published tenant reviews. Requires the building's slug — call search_buildings first if you only have an address. The returned url (anchored at #reviews) has every review in full text.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.lucidrents/building-intelligence, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 52 days ago. The registry entry · lucidrents.com