OwnerRez MCP by usefulapi
REMOTE · OWNERREZ.USEFULAPI.IO
Manage OwnerRez properties, bookings, guests, quotes and inquiries.
Available components
Last scanned (22 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_recent_payments_and_quotes” functional
- New prompt “create_quotes_or_bookings_and_add_or_update_guests” functional
- New prompt “review_guest_inquiries_and_messages” functional
- New prompt “see_upcoming_arrivals_and_booking_details” functional
- New prompt “update_a_booking_or_reply_in_a_guest_thread” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 0
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 0
- Server version: 1.26.0 → 1.28.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.4 → 1.23.0 functional
- Server version: 1.22.3 → 1.22.4 functional
- Server version: 1.22.0 → 1.22.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://ownerrez.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ownerrez.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ownerrez.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/ownerrez/ |
| http (plaintext) | http://ownerrez.usefulapi.io/mcp | Inconclusive | 302 | http://ownerrez.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ownerrez_create_booking Create a booking ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Number of adults. |
| arrival | string | – | Arrival/check-in date (ISO-8601, e.g. 2026-08-01). |
| children | integer | – | Number of children. |
| departure | string | – | Departure/check-out date (ISO-8601). |
| fields | object | – | Additional documented OwnerRez fields to send in the JSON write body (merged with the typed fields above). |
| guest_id | integer | – | The guest id for the reservation. |
| notes | string | – | Notes on the booking. |
| property_id | integer | yes | The property being booked (required). |
No output schema declared.
No examples provided.
ownerrez_create_guest Create a guest ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Additional documented OwnerRez fields to send in the JSON write body (merged with the typed fields above). |
| first_name | string | – | Guest first name. |
| last_name | string | – | Guest last name. |
| notes | string | – | Free-text notes on the guest. |
| opt_out_marketing_email | boolean | – | Opt this guest out of marketing email. |
| opt_out_marketing_sms | boolean | – | Opt this guest out of marketing SMS. |
No output schema declared.
No examples provided.
ownerrez_create_message Create a message ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The message text/body (required). |
| booking_id | integer | – | The booking this message relates to. |
| fields | object | – | Additional documented OwnerRez fields to send in the JSON write body (merged with the typed fields above). |
No output schema declared.
No examples provided.
ownerrez_create_quote Create a quote ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Number of adults. |
| arrival | string | – | Arrival/check-in date (ISO-8601). |
| children | integer | – | Number of children. |
| departure | string | – | Departure/check-out date (ISO-8601). |
| fields | object | – | Additional documented OwnerRez fields to send in the JSON write body (merged with the typed fields above). |
| guest_id | integer | – | The guest id, if quoting for an existing guest. |
| property_id | integer | yes | The property to quote (required). |
No output schema declared.
No examples provided.
ownerrez_get_booking Get a booking ~87
Fetch a single booking by id. OwnerRez API: GET /v2/bookings/{id}. Opt into embedded charges/guest/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The booking id. |
| include_charges | boolean | – | Include the charges breakdown. |
| include_guest | boolean | – | Include the embedded guest object. |
| include_tags | boolean | – | Include the tags collection. |
No output schema declared.
No examples provided.
ownerrez_get_guest Get a guest ~44
Fetch a single guest (contact) by id. OwnerRez API: GET /v2/guests/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The guest id. |
No output schema declared.
No examples provided.
ownerrez_get_listing Get a listing ~41
Fetch a single channel listing by id. OwnerRez API: GET /v2/listings/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The listing id. |
No output schema declared.
No examples provided.
ownerrez_get_me Get current user ~33
Return the authenticated OwnerRez user (verifies your credentials). OwnerRez API: GET /v2/users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ownerrez_get_payment Get a payment ~40
Fetch a single payment by id. OwnerRez API: GET /v2/payments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The payment id. |
No output schema declared.
No examples provided.
ownerrez_get_property Get a property ~44
Fetch a single property by id (includes time_zone). OwnerRez API: GET /v2/properties/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The property id. |
No output schema declared.
No examples provided.
ownerrez_get_quote Get a quote ~40
Fetch a single quote by id. OwnerRez API: GET /v2/quotes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The quote id. |
No output schema declared.
No examples provided.
ownerrez_list_bookings List bookings ~326
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start of the arrival/stay date window (ISO-8601, e.g. 2026-07-01). |
| include_cancellation_policy | boolean | – | Include the cancellation-policy detail. |
| include_charges | boolean | – | Include the charges breakdown on each booking. |
| include_fields | boolean | – | Include the custom-fields collection on each booking. |
| include_guest | boolean | – | Include the embedded guest object on each booking. |
| include_tags | boolean | – | Include the tags collection on each booking. |
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
| property_ids | string | – | Comma-separated property id(s) to filter by, e.g. "123" or "123,456". |
| since_utc | string | – | Only bookings created/updated on or after this UTC timestamp (ISO-8601). |
| status | string | – | Filter by booking status. |
| to | string | – | End of the arrival/stay date window (ISO-8601). |
No output schema declared.
No examples provided.
ownerrez_list_field_definitions List custom-field definitions ~111
List custom-field definitions available in the account (the schema for custom fields on properties/bookings/guests). OwnerRez API: GET /v2/fielddefinitions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_guests List guests ~258
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| created_since_utc | string | – | Only guests created on or after this UTC timestamp (ISO-8601). Required unless q is set. |
| from | string | – | Filter to guests departing on or after this date (ISO-8601). |
| include_fields | boolean | – | Include the custom-fields collection on each guest. |
| include_tags | boolean | – | Include the tags collection on each guest. |
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
| q | string | – | Search query across guest name/email (required unless created_since_utc is set). |
| to | string | – | Filter to guests arriving on or before this date (ISO-8601). |
No output schema declared.
No examples provided.
ownerrez_list_inquiries List inquiries ~104
List guest inquiries (pre-booking leads). OwnerRez API: GET /v2/inquiries. Use `params` for documented filters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_listing_sites List listing sites ~108
List the listing sites (channels, e.g. Airbnb, Vrbo) known to OwnerRez. OwnerRez API: GET /v2/listingsites.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_listings List listings ~120
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_messages List messages ~107
List messages from guest-communication threads. OwnerRez API: GET /v2/messages. Use `params` for documented filters (e.g. booking_id).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_owners List owners ~106
List property owners. OwnerRez API: GET /v2/owners. Returns { items, count, limit, offset, next_page_url }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_payments List payments ~108
List payments. OwnerRez API: GET /v2/payments. Use `params` for documented filters (e.g. booking_id, since_utc).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_list_properties List properties ~236
List rental properties. OwnerRez API: GET /v2/properties. Returns the pageable envelope { items, count, limit, offset, next_page_url }.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Filter by active status (true = only active properties). |
| availability_end_date | string | – | Filter by availability end date (ISO-8601). |
| availability_start_date | string | – | Filter by availability start date (ISO-8601, e.g. 2026-07-01). |
| include_fields | boolean | – | Include the custom-fields collection on each property. |
| include_listing_numbers | boolean | – | Include channel listing numbers on each property. |
| include_tags | boolean | – | Include the tags collection on each property. |
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
| payment_method_id | integer | – | Filter by applicable payment method id. |
No output schema declared.
No examples provided.
ownerrez_list_quotes List quotes ~124
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max items to return per page (default set by OwnerRez, typically 10). |
| offset | integer | – | Number of items to skip (for paging; combine with limit). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
ownerrez_request Raw read request ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Full API path after the host, starting with "/", e.g. "/v2/properties?limit=1". |
No output schema declared.
No examples provided.
ownerrez_update_booking Update a booking ~164
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).
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | New adult count. |
| arrival | string | – | New arrival date (ISO-8601). |
| children | integer | – | New child count. |
| departure | string | – | New departure date (ISO-8601). |
| fields | object | – | Additional documented OwnerRez fields to send in the JSON write body (merged with the typed fields above). |
| id | integer | yes | The booking id to update (required). |
| notes | string | – | New notes value. |
No output schema declared.
No examples provided.
ownerrez_update_guest Update a guest ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Additional documented OwnerRez fields to send in the JSON write body (merged with the typed fields above). |
| first_name | string | – | New first name. |
| id | integer | yes | The guest id to update (required). |
| last_name | string | – | New last name. |
| notes | string | – | New notes value. |
| opt_out_marketing_email | boolean | – | Opt-out flag for marketing email. |
| opt_out_marketing_sms | boolean | – | Opt-out flag for marketing SMS. |
No output schema declared.
No examples provided.
How do I install the OwnerRez MCP by usefulapi server?
OwnerRez MCP by usefulapi is a hosted endpoint at https://ownerrez.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ownerrez.usefulapi.io
claude mcp add --transport http io-usefulapi-ownerrez 'https://ownerrez.usefulapi.io/mcp'
What is the OwnerRez MCP by usefulapi server?
OwnerRez MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ownerrez. Manage OwnerRez properties, bookings, guests, quotes and inquiries. This page covers its hosted endpoint (https://ownerrez.usefulapi.io/mcp).
Is the OwnerRez MCP by usefulapi server safe to use?
OwnerRez MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OwnerRez MCP by usefulapi server expose?
OwnerRez MCP by usefulapi exposes 25 tools: ownerrez_get_me, ownerrez_list_properties, ownerrez_get_property, ownerrez_list_bookings, ownerrez_get_booking, and 20 more. Their descriptions and schemas cost roughly 3,165 tokens of context every time the server is loaded.
Does the OwnerRez MCP by usefulapi server require authentication?
Its publisher declares no required credentials for OwnerRez MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the OwnerRez MCP by usefulapi server still maintained?
OwnerRez MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the OwnerRez MCP by usefulapi server?
VerifyMCP ran 4 checks on OwnerRez MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about OwnerRez MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.