OwnerRez MCP by usefulapi
io.usefulapi/ownerrezusefulapi.iostreamable-httpv1.41.4Scanned
Manage OwnerRez properties, bookings, guests, quotes and inquiries.
25 tools: 6 can delete or cancel things, 1 change things and 18 only read.
- Reads private data · 4
- Reads text others write · 1
- Can send data out · 1
- 2 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
7 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the OwnerRez MCP by usefulapi can do
The OwnerRez MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 25 tools. It can delete or cancel things (6 tools: ownerrez_create_guest, ownerrez_update_guest, ownerrez_create_booking, ownerrez_update_booking and 2 more) and create or change data (1 tool: ownerrez_request). 18 tools only read.
4 tools read private data (ownerrez_get_me, ownerrez_list_guests, ownerrez_get_guest and 1 more); 1 tool brings in text other people can write (ownerrez_list_messages); 1 tool can send data out of your system (ownerrez_create_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Oct 25, 2026, version 1.41.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
25 tools
Deletes or cancels 6Claude Code: deny
ownerrez_create_bookingMUTATES OwnerRez data: creates a new booking (reservation).No findings
Why it is in this group
- The name "ownerrez_create_booking" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES OwnerRez data: creates a new booking (reservation). OwnerRez API: POST /v2/bookings (JSON). A booking ties a guest to a property for a date range; the exact charge/quote shape is account-specific, so pass extra documented fields via `fields`. Returns the created booking.
Annotations the server declares
- title: Create a booking
- destructiveHint: true
ownerrez_create_guestMUTATES OwnerRez data: creates a new guest (contact).No findings
Why it is in this group
- The name "ownerrez_create_guest" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES OwnerRez data: creates a new guest (contact). OwnerRez API: POST /v2/guests (JSON). Emails/phones/addresses are arrays of objects — pass them via the `fields` passthrough (e.g. email_addresses:[{address:"a@b.com"}]). Returns the created guest.
Annotations the server declares
- title: Create a guest
- destructiveHint: true
ownerrez_create_messageMUTATES OwnerRez data: posts a message into a guest-communication thread.Can send data outNo findings
Why it is in this group
- The name "ownerrez_create_message" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "ownerrez_create_message" says "create" and "message": it writes something other people read.
Description, as the server wrote it MUTATES OwnerRez data: posts a message into a guest-communication thread. OwnerRez API: POST /v2/messages (JSON). The exact thread/booking linkage is account-specific — pass extra documented fields (e.g. thread_id, booking_id) via `fields`. Returns the created message.
Annotations the server declares
- title: Create a message
- destructiveHint: true
ownerrez_create_quoteMUTATES OwnerRez data: creates a quote for a property + date range (the pre-booking pricing document).No findings
Why it is in this group
- The name "ownerrez_create_quote" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES OwnerRez data: creates a quote for a property + date range (the pre-booking pricing document). OwnerRez API: POST /v2/quotes (JSON). The full quote/charge shape is account-specific — pass extra documented fields via `fields`. Returns the created quote.
Annotations the server declares
- title: Create a quote
- destructiveHint: true
ownerrez_update_bookingMUTATES OwnerRez data: updates an existing booking.No findings
Why it is in this group
- The name "ownerrez_update_booking" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES OwnerRez data: updates an existing booking. OwnerRez API: PATCH /v2/bookings/{id} (JSON — only included fields change). Use the `fields` passthrough for any documented field (dates, guest counts, notes, status).
Annotations the server declares
- title: Update a booking
- destructiveHint: true
ownerrez_update_guestMUTATES OwnerRez data: updates an existing guest.No findings
Why it is in this group
- The name "ownerrez_update_guest" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it MUTATES OwnerRez data: updates an existing guest. OwnerRez API: PATCH /v2/guests/{id} (JSON — only included fields change). Use the `fields` passthrough for arrays (email_addresses/phones/addresses) and any other documented field.
Annotations the server declares
- title: Update a guest
- destructiveHint: true
Changes things 1Claude Code: ask
ownerrez_requestPower-user escape hatch: GET any OwnerRez API path not wrapped by a dedicated tool.1 finding
Why it is in this group
- The name "ownerrez_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "ownerrez_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "ownerrez_request" says "request": a word for a change.
Description, as the server wrote it Power-user escape hatch: GET any OwnerRez API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the host, starting with a slash, INCLUDING any query string, e.g. "/v2/propertysearch?query=beach" or "/v2/bookings/123". Returns the parsed JSON.
Annotations the server declares
- title: Raw read request
- readOnlyHint: true
Only reads 18Show 18 read-only tools
ownerrez_get_bookingFetch a single booking by id.No findings
Why it is in this group
- The name "ownerrez_get_booking" says "get": a word for reading.
Description, as the server wrote it Fetch a single booking by id. OwnerRez API: GET /v2/bookings/{id}. Opt into embedded charges/guest/tags.
Annotations the server declares
- title: Get a booking
- readOnlyHint: true
ownerrez_get_guestFetch a single guest (contact) by id.Reads private dataNo findings
Why it is in this group
- The name "ownerrez_get_guest" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it Fetch a single guest (contact) by id. OwnerRez API: GET /v2/guests/{id}.
Annotations the server declares
- title: Get a guest
- readOnlyHint: true
ownerrez_get_listingFetch a single channel listing by id.No findings
Why it is in this group
- The name "ownerrez_get_listing" says "get": a word for reading.
Description, as the server wrote it Fetch a single channel listing by id. OwnerRez API: GET /v2/listings/{id}.
Annotations the server declares
- title: Get a listing
- readOnlyHint: true
ownerrez_get_meReturn the authenticated OwnerRez user (verifies your credentials).Reads private data1 finding
Why it is in this group
- The name "ownerrez_get_me" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "credential": it reads secrets.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...henticated OwnerRez user (verifies your credentials). OwnerRez API: GET /v2/users/me."
Description, as the server wrote it Return the authenticated OwnerRez user (verifies your credentials). OwnerRez API: GET /v2/users/me.
Annotations the server declares
- title: Get current user
- readOnlyHint: true
ownerrez_get_paymentFetch a single payment by id.No findings
Why it is in this group
- The name "ownerrez_get_payment" says "get": a word for reading.
Description, as the server wrote it Fetch a single payment by id. OwnerRez API: GET /v2/payments/{id}.
Annotations the server declares
- title: Get a payment
- readOnlyHint: true
ownerrez_get_propertyFetch a single property by id (includes time_zone).No findings
Why it is in this group
- The name "ownerrez_get_property" says "get": a word for reading.
Description, as the server wrote it Fetch a single property by id (includes time_zone). OwnerRez API: GET /v2/properties/{id}.
Annotations the server declares
- title: Get a property
- readOnlyHint: true
ownerrez_get_quoteFetch a single quote by id.No findings
Why it is in this group
- The name "ownerrez_get_quote" says "get": a word for reading.
Description, as the server wrote it Fetch a single quote by id. OwnerRez API: GET /v2/quotes/{id}.
Annotations the server declares
- title: Get a quote
- readOnlyHint: true
ownerrez_list_bookingsList bookings (reservations).No findings
Why it is in this group
- The name "ownerrez_list_bookings" says "list": a word for reading.
Description, as the server wrote it List bookings (reservations). OwnerRez API: GET /v2/bookings. Filter by property, date range, changed-since, and status; opt into embedded charges/guest/tags. Returns { items, count, limit, offset, next_page_url }.
Annotations the server declares
- title: List bookings
- readOnlyHint: true
ownerrez_list_field_definitionsList custom-field definitions available in the account (the schema for custom fields on properties/bookings/guests).No findings
Why it is in this group
- The name "ownerrez_list_field_definitions" says "list": a word for reading.
Description, as the server wrote it List custom-field definitions available in the account (the schema for custom fields on properties/bookings/guests). OwnerRez API: GET /v2/fielddefinitions.
Annotations the server declares
- title: List custom-field definitions
- readOnlyHint: true
ownerrez_list_guestsList guests (contacts).Reads private dataNo findings
Why it is in this group
- The name "ownerrez_list_guests" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List guests (contacts). OwnerRez API: GET /v2/guests. NOTE: OwnerRez REQUIRES either `q` (search) or `created_since_utc` on this endpoint. Returns { items, count, limit, offset, next_page_url }.
Annotations the server declares
- title: List guests
- readOnlyHint: true
ownerrez_list_inquiriesList guest inquiries (pre-booking leads).No findings
Why it is in this group
- The name "ownerrez_list_inquiries" says "list": a word for reading.
Description, as the server wrote it List guest inquiries (pre-booking leads). OwnerRez API: GET /v2/inquiries. Use `params` for documented filters.
Annotations the server declares
- title: List inquiries
- readOnlyHint: true
ownerrez_list_listing_sitesList the listing sites (channels, e.g.No findings
Why it is in this group
- The name "ownerrez_list_listing_sites" says "list": a word for reading.
Description, as the server wrote it List the listing sites (channels, e.g. Airbnb, Vrbo) known to OwnerRez. OwnerRez API: GET /v2/listingsites.
Annotations the server declares
- title: List listing sites
- readOnlyHint: true
ownerrez_list_listingsList channel listings (a property's presence on a listing site such as Airbnb/Vrbo).No findings
Why it is in this group
- The name "ownerrez_list_listings" says "list": a word for reading.
Description, as the server wrote it List channel listings (a property's presence on a listing site such as Airbnb/Vrbo). OwnerRez API: GET /v2/listings. Returns { items, count, limit, offset, next_page_url }.
Annotations the server declares
- title: List listings
- readOnlyHint: true
ownerrez_list_messagesList messages from guest-communication threads.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "ownerrez_list_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "ownerrez_list_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "ownerrez_list_messages" says "list" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List messages from guest-communication threads. OwnerRez API: GET /v2/messages. Use `params` for documented filters (e.g. booking_id).
Annotations the server declares
- title: List messages
- readOnlyHint: true
ownerrez_list_ownersList property owners.No findings
Why it is in this group
- The name "ownerrez_list_owners" says "list": a word for reading.
Description, as the server wrote it List property owners. OwnerRez API: GET /v2/owners. Returns { items, count, limit, offset, next_page_url }.
Annotations the server declares
- title: List owners
- readOnlyHint: true
ownerrez_list_paymentsList payments.No findings
Why it is in this group
- The name "ownerrez_list_payments" says "list": a word for reading.
Description, as the server wrote it List payments. OwnerRez API: GET /v2/payments. Use `params` for documented filters (e.g. booking_id, since_utc).
Annotations the server declares
- title: List payments
- readOnlyHint: true
ownerrez_list_propertiesList rental properties.No findings
Why it is in this group
- The name "ownerrez_list_properties" says "list": a word for reading.
Description, as the server wrote it List rental properties. OwnerRez API: GET /v2/properties. Returns the pageable envelope { items, count, limit, offset, next_page_url }.
Annotations the server declares
- title: List properties
- readOnlyHint: true
ownerrez_list_quotesList quotes.No findings
Why it is in this group
- The name "ownerrez_list_quotes" says "list": a word for reading.
Description, as the server wrote it List quotes. OwnerRez API: GET /v2/quotes. Returns { items, count, limit, offset, next_page_url }. Use the `params` passthrough for documented filters (e.g. property_id, guest_id).
Annotations the server declares
- title: List quotes
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__ownerrez__ownerrez_create_message"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ownerrez.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://ownerrez.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Warnownerrez_request
The server marks "ownerrez_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "ownerrez_request" says "request": a word for a change.
- Infoownerrez_get_me
The description mentions "credentials".
What this check looks forMatched text
description: "...henticated OwnerRez user (verifies your credentials). OwnerRez API: GET /v2/users/me."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ownerrez.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://ownerrez.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Tools24 added, 24 removed.+24 added−24 removedView diff
- Added:ownerrez_create_bookingDeletes or cancels
- Added:ownerrez_create_guestDeletes or cancels
- Added:ownerrez_create_messageDeletes or cancels
- Added:ownerrez_create_quoteDeletes or cancels
- Added:ownerrez_get_bookingOnly reads
- Added:ownerrez_get_guestOnly reads
- Added:ownerrez_get_listingOnly reads
- Added:ownerrez_get_meOnly reads
- Added:ownerrez_get_paymentOnly reads
- Added:ownerrez_get_propertyOnly reads
- Added:ownerrez_get_quoteOnly reads
- Added:ownerrez_list_bookingsOnly reads
- Added:ownerrez_list_field_definitionsOnly reads
- Added:ownerrez_list_guestsOnly reads
- Added:ownerrez_list_inquiriesOnly reads
- Added:ownerrez_list_listing_sitesOnly reads
- Added:ownerrez_list_listingsOnly reads
- Added:ownerrez_list_messagesOnly reads
- Added:ownerrez_list_ownersOnly reads
- Added:ownerrez_list_paymentsOnly reads
- Added:ownerrez_list_propertiesOnly reads
- Added:ownerrez_list_quotesOnly reads
- Added:ownerrez_update_bookingDeletes or cancels
- Added:ownerrez_update_guestDeletes or cancels
- Removed:create_booking
- Removed:create_guest
- Removed:create_message
- Removed:create_quote
- Removed:get_booking
- Removed:get_guest
- Removed:get_listing
- Removed:get_me
- Removed:get_payment
- Removed:get_property
- Removed:get_quote
- Removed:list_bookings
- Removed:list_field_definitions
- Removed:list_guests
- Removed:list_inquiries
- Removed:list_listing_sites
- Removed:list_listings
- Removed:list_messages
- Removed:list_owners
- Removed:list_payments
- Removed:list_properties
- Removed:list_quotes
- Removed:update_booking
- Removed:update_guest
Install
Pinned to version 1.41.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http ownerrez https://ownerrez.usefulapi.io/mcpclaude mcp add --transport http ownerrez https://ownerrez.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ownerrez__ownerrez_get_me",
"mcp__ownerrez__ownerrez_list_properties",
"mcp__ownerrez__ownerrez_get_property",
"mcp__ownerrez__ownerrez_list_bookings",
"mcp__ownerrez__ownerrez_get_booking",
"mcp__ownerrez__ownerrez_list_guests",
"mcp__ownerrez__ownerrez_get_guest",
"mcp__ownerrez__ownerrez_list_quotes",
"mcp__ownerrez__ownerrez_get_quote",
"mcp__ownerrez__ownerrez_list_listings",
"mcp__ownerrez__ownerrez_get_listing",
"mcp__ownerrez__ownerrez_list_listing_sites",
"mcp__ownerrez__ownerrez_list_owners",
"mcp__ownerrez__ownerrez_list_inquiries",
"mcp__ownerrez__ownerrez_list_messages",
"mcp__ownerrez__ownerrez_list_payments",
"mcp__ownerrez__ownerrez_get_payment",
"mcp__ownerrez__ownerrez_list_field_definitions"
],
"ask": [
"mcp__ownerrez__ownerrez_request"
],
"deny": [
"mcp__ownerrez__ownerrez_create_guest",
"mcp__ownerrez__ownerrez_update_guest",
"mcp__ownerrez__ownerrez_create_booking",
"mcp__ownerrez__ownerrez_update_booking",
"mcp__ownerrez__ownerrez_create_quote",
"mcp__ownerrez__ownerrez_create_message"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ownerrez. Review it before you use it.
Capability tags behind 5 rules
- mcp__ownerrez__ownerrez_get_me private-data
- mcp__ownerrez__ownerrez_list_guests private-data
- mcp__ownerrez__ownerrez_get_guest private-data
- mcp__ownerrez__ownerrez_list_messages private-data, untrusted-input
- mcp__ownerrez__ownerrez_create_message outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/ownerrez/verify?hash=ed4060d94e5fcb833a078380888da901d3cc7165255d322866ff65971576499a" | jq -e '.changed == false'Pinned hash ed4060d94e5f, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/ownerrez/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/ownerrez)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
OwnerRez MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the OwnerRez MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 25 tools, 7 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the OwnerRez MCP by usefulapi delete data?
- Yes. 6 tools can delete, cancel or revoke something: ownerrez_create_guest, ownerrez_update_guest, ownerrez_create_booking, ownerrez_update_booking, ownerrez_create_quote and ownerrez_create_message.
Can the OwnerRez MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the OwnerRez MCP by usefulapi have?
- 25 tools: 6 destructive, 1 write, 18 read. ownerrez_create_guest, ownerrez_update_guest, ownerrez_create_booking, ownerrez_update_booking, ownerrez_create_quote, ownerrez_create_message, ownerrez_request, ownerrez_get_me and 17 more.
Does the OwnerRez MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the OwnerRez MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ownerrez_create_message.
Has the OwnerRez MCP by usefulapi changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.