Home / MCP registry index / io.usefulapi/ezrentout

EZRentOut MCP by usefulapi

io.usefulapi/ezrentout in the official MCP registry. Endpoint https://ezrentout.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: MCP server for EZRentOut — rental orders, assets, customers, inventory and work orders.

We read its 59 tools on 2026-11-01. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http ezrentout https://ezrentout.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "ezrentout": {
      "url": "https://ezrentout.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"ezrentout","type":"http","url":"https://ezrentout.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

ezrentout_list_orders ezrentout_get_order ezrentout_get_order_history ezrentout_list_payment_options ezrentout_list_coupons ezrentout_list_customers ezrentout_get_customer ezrentout_search_member_by_email ezrentout_list_businesses ezrentout_get_business ezrentout_list_business_contacts ezrentout_get_business_contact ezrentout_list_customer_addresses ezrentout_list_business_addresses ezrentout_list_assets ezrentout_filter_assets ezrentout_search_assets ezrentout_get_asset ezrentout_get_asset_history ezrentout_get_asset_booked_dates ezrentout_list_asset_comments ezrentout_list_assets_in_service ezrentout_list_inventory ezrentout_get_inventory_item ezrentout_search_inventory ezrentout_get_inventory_history ezrentout_get_quantity_by_location ezrentout_list_asset_stock ezrentout_get_asset_stock ezrentout_list_users ezrentout_get_user ezrentout_get_user_checked_out_items ezrentout_list_locations ezrentout_get_location ezrentout_get_location_quantities ezrentout_list_groups ezrentout_list_subgroups ezrentout_list_bundles ezrentout_get_bundle ezrentout_list_vendors ezrentout_list_custom_fields ezrentout_list_purchase_orders ezrentout_get_purchase_order ezrentout_list_work_orders ezrentout_get_work_order ezrentout_list_work_order_types ezrentout_list_custom_reports ezrentout_create_customer ezrentout_create_order ezrentout_add_assets_to_order ezrentout_book_order ezrentout_add_order_custom_entry ezrentout_record_order_payment ezrentout_rent_out_order ezrentout_return_order ezrentout_add_asset_comment ezrentout_create_work_order ezrentout_start_work_order ezrentout_complete_work_order

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): fd5c15fa810f17f3. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-ezrentout/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-ezrentout)

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.