Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EZRentOut MCP by usefulapi

REMOTE · EZRENTOUT.USEFULAPI.IO

MCP server for EZRentOut — rental orders, assets, customers, inventory and work orders.

18 Trust /100

Last scanned (4 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 6 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability0
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.

What we tested

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 →

Changelog

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 −48
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 66

    First indexed and scored.

Diagnostics

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 6 Nov 2026 · Probed https://ezrentout.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 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
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 ezrentout.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://ezrentout.usefulapi.io/mcp Redirected 302 https://usefulapi.io/ezrentout/
http (plaintext) http://ezrentout.usefulapi.io/mcp Inconclusive 302 http://ezrentout.usefulapi.io/mcp
MCP tools · 59 exposed · ~4,801 tokens

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 →

Tool Tokens
ezrentout_add_asset_comment ~72

Add a comment to an asset, asset stock or inventory item. POST /assets/<ASSET#>/comments.api.

NameTypeReqDescription
asset_number–yesThe item number (Asset#).
contentstringyesThe comment text.
created_by_id––The user the comment is attributed to.

No output schema declared.

No examples provided.

ezrentout_add_assets_to_order ~85

Add assets (or bundles as <id>-b) to an existing order. PATCH /baskets/<ORDER#>/update_basket_from_show.api.

NameTypeReqDescription
asset_numbersarrayyesAsset numbers; a bundle as <bundle id>-b, e.g. 12, 25-b.
order_number–yesThe order number (Order#).

No output schema declared.

No examples provided.

ezrentout_add_order_custom_entry ~120

Add a custom line (a named amount, for example a delivery fee) to an order; it raises the order total. Not possible on sold, void, completed or cancelled orders. POST /baskets/<ORDER#>/custom_entries.api.

NameTypeReqDescription
amountnumberyesThe amount, in the account's currency.
commentsstring–Comments.
namestringyesName of the charge.
order_number–yesThe order number.
tax_freeboolean–true = no tax on this charge.

No output schema declared.

No examples provided.

ezrentout_book_order ~118

Reserve an order's assets for a period (books the order). EZRentOut may notify the customer according to the account's settings. PATCH /baskets/<ORDER#>/reservation.api.

NameTypeReqDescription
fromstringyesReservation start (mm/dd/yyyy).
from_timestring–Start time (hh:mm, 24 hours).
order_number–yesThe order number.
tostringyesReservation end (mm/dd/yyyy).
to_timestring–End time (hh:mm, 24 hours).

No output schema declared.

No examples provided.

ezrentout_complete_work_order ~48

Mark a work order complete; its assets may become available again. PATCH /tasks/<Work_Order#>/mark_complete.api.

NameTypeReqDescription
work_order_number–yesThe work order number.

No output schema declared.

No examples provided.

ezrentout_create_customer ~145

Create a customer (a person who rents). First and last name are required. Does not create an order. POST /customers.api.

NameTypeReqDescription
addressstring–Address line 1.
citystring–City.
countrystring–Two-letter country code, e.g. US.
descriptionstring–Notes about the customer.
emailstring–Email address.
first_namestringyesFirst name.
last_namestringyesLast name.
phone_numberstring–Phone number.
statestring–State or province.
zip_codestring–Zip or postal code.

No output schema declared.

No examples provided.

ezrentout_create_order ~186

Create a new rental order (a draft until it is booked or rented out) for a customer, optionally with assets and dates. If the customer belongs to several businesses, pass business_id. Does not rent anything out and does not charge. POST /baskets.api.

NameTypeReqDescription
asset_numbersarray–Assets to add (asset numbers; a bundle as <id>-b).
business_id––The business, when the contact is part of several.
customer_id–yesThe customer or business-contact id, from ezrentout_list_customers.
descriptionstring–Order description.
due_datestring–Due (return) date (mm/dd/yyyy).
expected_checkout_datestring–Expected check-out date (mm/dd/yyyy).
expected_checkout_timestring–Expected check-out time (hh:mm, 24 hours).

No output schema declared.

No examples provided.

ezrentout_create_work_order ~151

Create a work order with a title, type and due date, optionally for assets. By default the linked assets are marked unavailable (mark_items_unavailable). POST /tasks.api.

NameTypeReqDescription
asset_numbersarray–Assets the work order is for.
descriptionstring–Description.
due_datestringyesDue date (mm/dd/yyyy).
mark_items_unavailableboolean–Default true in EZRentOut: the assets cannot be rented while the work order is open.
prioritystring–Priority.
task_typestringyesThe work order type name, from ezrentout_list_work_order_types.
titlestringyesThe summary.

No output schema declared.

No examples provided.

ezrentout_filter_assets ~207

Assets by a status filter. status: available, assets_being_serviced, availability_range, checked_out (= currently rented out), group, location, overdue, possessions_of, possessions_of_email, reserved, product_model_number, items_in_order, reservation_starting_today, retired, update_time. Most filters need filter_param_val (a group or location id, a user id, an email, a model number, an order number; for availability_range two dates joined by ~). Not needed for available, checked_out, overdue, reserved, retired. GET /assets/filter.api.

NameTypeReqDescription
filter_param_valstring–The value the filter needs, if any.
include_custom_fieldsboolean–Also return the items' custom fields (default false).
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.
statusstringyesThe filter.

No output schema declared.

No examples provided.

ezrentout_get_asset ~101

One fixed asset by its asset number: details, group, location, status, rental prices, optionally service details and custom fields. GET /assets/<ASSET#>.api.

NameTypeReqDescription
asset_number–yesThe asset number (Asset#), from ezrentout_list_assets.
include_custom_fieldsboolean–Also return the items' custom fields (default false).
show_services_detailsboolean–Also return service (maintenance) data.

No output schema declared.

No examples provided.

ezrentout_get_asset_booked_dates ~56

The dates on which an asset, inventory item or asset stock is booked or reserved. GET /assets/<ASSET#>/booked_dates.api.

NameTypeReqDescription
asset_number–yesThe item number (Asset#).

No output schema declared.

No examples provided.

ezrentout_get_asset_history ~86

The check-in/check-out and change history of one asset (5 entries per page). GET /assets/<ASSET#>/history_paginate.api.

NameTypeReqDescription
asset_number–yesThe asset number.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_get_asset_stock ~59

One asset stock item by number. GET /stock_assets/<AssetStock#>.api.

NameTypeReqDescription
asset_number–yesThe asset stock number.
include_custom_fieldsboolean–Also return the items' custom fields (default false).

No output schema declared.

No examples provided.

ezrentout_get_bundle ~40

One bundle by id, with its items. GET /bundles/<BUNDLE#>.api.

NameTypeReqDescription
bundle_id–yesThe bundle id.

No output schema declared.

No examples provided.

ezrentout_get_business ~45

One business customer by id. GET /businesses/<BUSINESS#>.api.

NameTypeReqDescription
business_id–yesThe business id, from ezrentout_list_businesses.

No output schema declared.

No examples provided.

ezrentout_get_business_contact ~44

One business contact by id. GET /contacts/<CONTACT_ID>.api.

NameTypeReqDescription
contact_id–yesThe contact id, from ezrentout_list_business_contacts.

No output schema declared.

No examples provided.

ezrentout_get_customer ~56

One customer by id: name, email, phone, addresses, status, custom fields. GET /customers/<CUSTOMER_ID>.api.

NameTypeReqDescription
customer_id–yesThe customer id, from ezrentout_list_customers.

No output schema declared.

No examples provided.

ezrentout_get_inventory_history ~83

The stock movements (added, sold, transferred) of one inventory item. GET /inventory/<ASSET#>/history.api.

NameTypeReqDescription
asset_number–yesThe inventory item number.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_get_inventory_item ~65

One inventory item by item number, with its stock. GET /inventory/<ASSET#>.api.

NameTypeReqDescription
asset_number–yesThe inventory item number (Asset#).
include_custom_fieldsboolean–Also return the items' custom fields (default false).

No output schema declared.

No examples provided.

ezrentout_get_location ~34

One location by id. GET /locations/<LOCATION#>.api.

NameTypeReqDescription
location_id–yesThe location id.

No output schema declared.

No examples provided.

ezrentout_get_location_quantities ~51

The quantity of every asset, asset-stock and inventory item at one location. GET /locations/<LOCATION#>/quantities_by_asset_ids.api.

NameTypeReqDescription
location_id–yesThe location id.

No output schema declared.

No examples provided.

ezrentout_get_order ~69

One order by its order number: customer, status, dates, line items (order_line_items), sub-rent items, totals and payments. GET /baskets/<ORDER#>.api.

NameTypeReqDescription
order_number–yesThe order number (Order#), from ezrentout_list_orders.

No output schema declared.

No examples provided.

ezrentout_get_order_history ~46

The check-out / check-in history of one order. GET /baskets/<ORDER#>/history.api.

NameTypeReqDescription
order_number–yesThe order number (Order#).

No output schema declared.

No examples provided.

ezrentout_get_purchase_order ~43

One purchase order with its items. GET /purchase_orders/<PO#>.api.

NameTypeReqDescription
purchase_order_number–yesThe purchase order number (PO#).

No output schema declared.

No examples provided.

ezrentout_get_quantity_by_location ~63

The stock of an inventory or asset-stock item at one location. GET /locations/get_quantity_by_location.api.

NameTypeReqDescription
asset_id–yesThe item number (Asset#).
location_id–yesThe location id, from ezrentout_list_locations.

No output schema declared.

No examples provided.

ezrentout_get_user ~41

One user by id. GET /members/<USER_ID>.api.

NameTypeReqDescription
user_id–yesThe user id, from ezrentout_list_users.

No output schema declared.

No examples provided.

ezrentout_get_user_checked_out_items ~118

The assets currently checked out to one user (a read; the vendor API uses PUT for this lookup). PUT /members/<USER_ID>/checked_out_items.api?page=N with item_type in the form body.

NameTypeReqDescription
item_typestring–Only this item type, if the account uses one.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.
user_id–yesThe user id.

No output schema declared.

No examples provided.

ezrentout_get_work_order ~39

One work order by number. GET /tasks/<Work_Order#>.api.

NameTypeReqDescription
work_order_number–yesThe work order number.

No output schema declared.

No examples provided.

ezrentout_list_asset_comments ~98

The comments on one item (25 per page), optionally by one user. GET /assets/<ASSET#>/comments.api.

NameTypeReqDescription
asset_number–yesThe item number (Asset#).
created_by_id––Only comments by this user id.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_asset_stock ~89

List asset stock (bulk items tracked by quantity per location, 25 per page). GET /stock_assets.api.

NameTypeReqDescription
include_custom_fieldsboolean–Also return the items' custom fields (default false).
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_assets ~113

List fixed assets (the individually tracked rental items, 25 per page) with group, location and status. GET /assets.api.

NameTypeReqDescription
include_custom_fieldsboolean–Also return the items' custom fields (default false).
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.
show_image_urlsboolean–Also return document and image links of the items (default false).

No output schema declared.

No examples provided.

ezrentout_list_assets_in_service ~108

Assets currently in maintenance (25 per page), optionally only one service type or state. GET /assets/filter.api?for_service=true&status=assets_being_serviced.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.
service_statestring–Only this service state.
service_typestring–Only this service type name.

No output schema declared.

No examples provided.

ezrentout_list_bundles ~66

Bundles (items rented together, 25 per page). GET /bundles.api.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_business_addresses ~78

The shipping/billing addresses of one business. GET /businesses/<BUSINESS#>/shipping_addresses.api.

NameTypeReqDescription
business_id–yesThe business id.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_business_contacts ~64

List the contact persons of business customers (25 per page). GET /contacts.api.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_businesses ~128

List business customers (20 per page). Optional filter: all, active_businesses, inactive_businesses, checked_out_orders, active_customers, completed_orders (completed_orders needs filter_val, for example "> 50"). GET /businesses.api.

NameTypeReqDescription
filterstring–Filter name (default all).
filter_valstring–The comparison for completed_orders, for example > 50.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_coupons ~28

All pricing coupons of the company. GET /pricing_coupons.api.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ezrentout_list_custom_fields ~30

The custom fields defined for items (names and ids). GET /assets/custom_attributes.api.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ezrentout_list_custom_reports ~31

The saved custom reports (id, name, description). GET /reports/list_custom_reports.api.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ezrentout_list_customer_addresses ~77

The shipping/billing addresses of one customer. GET /customers/<CUSTOMER_ID>/shipping_addresses.api.

NameTypeReqDescription
customer_id–yesThe customer id.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_customers ~161

List customers (25 per page). Optional filter: email, category, taxed, non_taxed, inactive_customers, subscribed_emails, not_subscribed_emails, checked_out_orders, completed_orders, account_name. email, category, account_name and completed_orders (for example "> 50") need filter_val. GET /customers.api.

NameTypeReqDescription
filterstring–Filter name.
filter_valstring–The value for the filters that need one (an email address, a category, an account name, or a comparison such as > 50).
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_groups ~69

The asset groups (categories, 25 per page) with their items. GET /assets/classification_view.api.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_inventory ~86

List inventory (consumable items tracked by quantity, 25 per page). GET /inventory.api.

NameTypeReqDescription
include_custom_fieldsboolean–Also return the items' custom fields (default false).
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_locations ~79

The company's locations (25 per page); status all, active or inactive. GET /locations/get_line_item_locations.api.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.
statusstring–Default all.

No output schema declared.

No examples provided.

ezrentout_list_orders ~81

List all rental orders (25 per page) with status, customer and dates. Paged: add 1 to page for the next one. GET /baskets.api.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_payment_options ~36

The payment options (cash, check, ...) that ezrentout_record_order_payment accepts. GET /payment_options.api.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ezrentout_list_purchase_orders ~22

All purchase orders. GET /purchase_orders.api.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ezrentout_list_subgroups ~43

All subgroups, or those of one group. GET /groups/get_sub_groups.api.

NameTypeReqDescription
group_id––Only the subgroups of this group.

No output schema declared.

No examples provided.

ezrentout_list_users ~111

The company's users (staff/admins, 25 per page). Filter by email, employee_identification_number or status (filter_val: active, inactive, login, non_login, all). GET /members.api.

NameTypeReqDescription
filterstring–Filter name.
filter_valstring–The value for the filter.
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

ezrentout_list_vendors ~64

The company's vendors/suppliers (25 per page). GET /assets/vendors.api.

NameTypeReqDescription
pageinteger–Page number, 1-based (default 1). Replies include the total number of pages; ask for the next page by adding 1.

No output schema declared.

No examples provided.

Install

How do I install the EZRentOut MCP by usefulapi server?

EZRentOut MCP by usefulapi is a hosted endpoint at https://ezrentout.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 · ezrentout.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-ezrentout 'https://ezrentout.usefulapi.io/mcp'
Common questions

What is the EZRentOut MCP by usefulapi server?

EZRentOut MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ezrentout. MCP server for EZRentOut, rental orders, assets, customers, inventory and work orders. This page covers its hosted endpoint (https://ezrentout.usefulapi.io/mcp).

Is the EZRentOut MCP by usefulapi server safe to use?

EZRentOut 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 EZRentOut MCP by usefulapi server expose?

EZRentOut MCP by usefulapi exposes 59 tools: ezrentout_list_orders, ezrentout_get_order, ezrentout_get_order_history, ezrentout_list_payment_options, ezrentout_list_coupons, and 54 more. Their descriptions and schemas cost roughly 4,801 tokens of context every time the server is loaded.

Does the EZRentOut MCP by usefulapi server require authentication?

Its publisher declares no required credentials for EZRentOut 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 EZRentOut MCP by usefulapi server still maintained?

EZRentOut MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 EZRentOut MCP by usefulapi server?

VerifyMCP ran 4 checks on EZRentOut 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 EZRentOut 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.