Home / MCP registry index / io.usefulapi/ownerrez
OwnerRez MCP by usefulapi
io.usefulapi/ownerrez in the official MCP registry.
Endpoint https://ownerrez.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Manage OwnerRez properties, bookings, guests, quotes and inquiries.
We read its 25 tools on 2026-10-26. 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
ownerrez_get_me ownerrez_list_properties ownerrez_get_property ownerrez_list_bookings ownerrez_get_booking ownerrez_list_guests ownerrez_get_guest ownerrez_list_quotes ownerrez_get_quote ownerrez_list_listings ownerrez_get_listing ownerrez_list_listing_sites ownerrez_list_owners ownerrez_list_inquiries ownerrez_list_messages ownerrez_list_payments ownerrez_get_payment ownerrez_list_field_definitions ownerrez_request ownerrez_create_guest ownerrez_update_guest ownerrez_create_booking ownerrez_update_booking ownerrez_create_quote ownerrez_create_message
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-ownerrez)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.