Buildium MCP by usefulapi
REMOTE · BUILDIUM.USEFULAPI.IO
Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.
Available components
Last scanned (28 minutes ago)
Scores higher than 3% of remote servers
Reachable. Last reached 22 Nov 2026.
Category CRM and Sales
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 −59
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +2
- Authorization: partial → pass ▲ security
- Tool “buildium_list_bills” rewrote its description, which is the text the model reads security
- Tool “buildium_list_work_orders” rewrote its description, which is the text the model reads security
- MCP protocol: fail → pass ▲ functional
- Stability: pass → 0.93 functional
- New prompt “check_which_leases_end_soon” functional
- New prompt “create_a_work_order_for_a_vendor” functional
- New prompt “find_tenants_who_owe_rent” functional
- New prompt “review_open_work_orders_by_priority” functional
- New prompt “update_to_do_tasks_and_work_orders” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.33.0 → 1.34.0 functional
- Server version: 1.32.0 → 1.33.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.3 → 1.31.0 functional
- Server version: 1.30.2 → 1.30.3 functional
- “buildium_list_bills” reworded the description of “entity_id” cosmetic
- “buildium_list_bills” reworded the description of “vendor_id” cosmetic
- “buildium_list_work_orders” reworded the description of “amount_from” cosmetic
- “buildium_list_work_orders” reworded the description of “amount_to” cosmetic
- “buildium_list_work_orders” reworded the description of “assigned_to_id” cosmetic
- “buildium_list_work_orders” reworded the description of “entity_id” cosmetic
- “buildium_list_work_orders” reworded the description of “statuses” cosmetic
- “buildium_list_work_orders” reworded the description of “task_category_id” cosmetic
- “buildium_list_work_orders” reworded the description of “task_ids” cosmetic
- “buildium_list_work_orders” reworded the description of “unit_agreement_id” cosmetic
- “buildium_list_work_orders” reworded the description of “unit_id” cosmetic
- “buildium_list_work_orders” reworded the description of “vendor_ids” cosmetic
- 30 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 +1
- 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.25.0 → 1.28.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 +1
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.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 22 Nov 2026 · Probed https://buildium.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 buildium.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://buildium.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/buildium/ |
| http (plaintext) | http://buildium.usefulapi.io/mcp | Inconclusive | 302 | http://buildium.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 →
buildium_create_todo_task Create a to-do task ~170
Create an internal to-do task assigned to a staff user, optionally tied to a property/unit and category, with a due date. Buildium: POST /v1/tasks/todorequests.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_user_id | integer | yes | Staff user id assigned to the task. |
| category_id | integer | – | Task category id. |
| description | string | – | Task description. |
| due_date | string | – | Due date, YYYY-MM-DD. |
| priority | string | yes | Priority. |
| property_id | integer | – | Active property id. |
| status | string | yes | Status. |
| subcategory_id | integer | – | Task subcategory id. |
| title | string | yes | Task title (max 127). |
| unit_id | integer | – | Unit id (must belong to property_id). |
No output schema declared.
No examples provided.
buildium_create_work_order Create a work order ~278
Create a work order for a vendor. Attach it to an existing task (task_id) or create a new task with it (task: title, priority, status, assigned staff user, optional due date/property/unit). vendor_id and entry_allowed are required. Line items are optional (quantity x unit price, optional GL account). Buildium: POST /v1/workorders.
| Name | Type | Req | Description |
|---|---|---|---|
| chargeable_to | string | – | Who will be charged for the work (max 100). |
| entry_allowed | string | yes | Whether entry to the unit is allowed. |
| entry_contact_ids | array | – | Entry contact user ids (RentalTenant, AssociationOwner, Staff or RentalOwner). |
| entry_notes | string | – | Notes on entering the unit. |
| invoice_number | string | – | Vendor invoice/reference number (max 50). |
| line_items | array | – | Work order line items. |
| task | object | – | A new task to create and link to this work order (instead of task_id). |
| task_id | integer | – | Existing task to attach this work order to. |
| title | string | – | Work order title (max 127 chars). |
| vendor_id | integer | yes | Vendor id doing the work. |
| vendor_notes | string | – | Notes for the vendor. |
| work_details | string | – | Description of the work. |
No output schema declared.
No examples provided.
buildium_get_lease Get a lease ~55
Fetch one lease by id, including tenants, cosigners, account details and move-out data. Buildium: GET /v1/leases/{leaseId}.
| Name | Type | Req | Description |
|---|---|---|---|
| lease_id | integer | yes | The lease id. |
No output schema declared.
No examples provided.
buildium_get_rental_property Get a rental property ~45
Fetch one rental property by id. Buildium: GET /v1/rentals/{propertyId}.
| Name | Type | Req | Description |
|---|---|---|---|
| property_id | integer | yes | The rental property id. |
No output schema declared.
No examples provided.
buildium_get_rental_unit Get a rental unit ~47
Fetch one rental unit by id. Buildium: GET /v1/rentals/units/{unitId}.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_id | integer | yes | The rental unit id. |
No output schema declared.
No examples provided.
buildium_get_tenant Get a tenant ~45
Fetch one rental tenant by id. Buildium: GET /v1/leases/tenants/{tenantId}.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | integer | yes | The tenant id. |
No output schema declared.
No examples provided.
buildium_get_work_order Get a work order ~45
Fetch one work order by id. Buildium: GET /v1/workorders/{workOrderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| work_order_id | integer | yes | The work order id. |
No output schema declared.
No examples provided.
buildium_list_applicants List applicants ~314
List rental applicants with contact details, status and their applications. Filter by application status, unit, name, email, submission date or entity. Buildium: GET /v1/applicants.
| Name | Type | Req | Description |
|---|---|---|---|
| application_statuses | array | – | Application statuses. |
| string | – | Email contains this value. | |
| entity_id | integer | – | Property or rental owner id (per entity_type). |
| entity_type | string | – | Scope by entity type; required with entity_id. |
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| name | string | – | Applicant name contains this value. |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| submitted_from | string | – | Application submitted on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| submitted_to | string | – | Application submitted on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| unit_ids | array | – | Filter to these unit ids. |
No output schema declared.
No examples provided.
buildium_list_associations List associations ~225
List community/HOA associations with address, manager, reserve, fiscal year and operating bank account. Buildium: GET /v1/associations.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Filter to these association ids. |
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| location | string | – | City or state contains this value. |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| operating_bank_account_ids | array | – | Filter to these operating bank account ids. |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| status | string | – | Association status (both if omitted). |
No output schema declared.
No examples provided.
buildium_list_bills List bills ~312
List vendor bills (accounts payable) with dates, memo, vendor, linked work order, reference number, approval status and lines. Read-only. Supply entity_type with entity_id (Rental for a property). paid_date_from/to filter the payment date, not the bill or due date, and must be YYYY-MM-DD with from at most to. For sorting use bill fields such as Date, DueDate, PaidDate or Id. Buildium: GET /v1/bills.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_statuses | array | – | Approval statuses. |
| entity_id | integer | – | The entity with line items on the bill, matching entity_type id (positive 32-bit integer). |
| entity_type | string | – | Scope by entity type; required with entity_id. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| paid_date_from | string | – | Paid on or after — formatted YYYY-MM-DD. |
| paid_date_to | string | – | Paid on or before — formatted YYYY-MM-DD. |
| paid_status | string | – | Paid status. |
| reference_number | string | – | Reference number contains this value. |
| vendor_id | integer | – | The vendor id (positive 32-bit integer). |
No output schema declared.
No examples provided.
buildium_list_gl_accounts List general ledger accounts ~145
List the chart of accounts: GL accounts with number, name, type/subtype, sub-accounts and bank/credit-card flags. Useful for finding the gl_account_id for work order line items. Buildium: GET /v1/glaccounts.
| Name | Type | Req | Description |
|---|---|---|---|
| account_types | array | – | Account types. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
No output schema declared.
No examples provided.
buildium_list_lease_transactions List lease transactions ~202
Read a lease's ledger: charges, payments, credits, refunds, deposits and other transactions with date, type, total amount and journal lines. Read-only — this server never posts to a ledger. Buildium: GET /v1/leases/{leaseId}/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| lease_id | integer | yes | The lease id. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| transaction_date_from | string | – | Transaction date on or after — formatted YYYY-MM-DD. |
| transaction_date_to | string | – | Transaction date on or before — formatted YYYY-MM-DD. |
| transaction_types | array | – | Transaction types to include. |
No output schema declared.
No examples provided.
buildium_list_leases List leases ~358
List leases with unit, dates, lease type/status, current tenants, rent/deposit account details and eviction flag. Filter by property, owner, unit number, tenant name, dates, lease type or status (Active/Past/Future). Buildium: GET /v1/leases.
| Name | Type | Req | Description |
|---|---|---|---|
| created_from | string | – | Created on or after — YYYY-MM-DD HH:MM:SS. |
| created_to | string | – | Created on or before — YYYY-MM-DD HH:MM:SS. |
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| lease_date_from | string | – | Lease start date on or after — formatted YYYY-MM-DD. |
| lease_date_to | string | – | Lease end date on or before — formatted YYYY-MM-DD. |
| lease_statuses | array | – | Lease term statuses. |
| lease_types | array | – | Lease types. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| property_ids | array | – | Filter to these property ids. |
| rental_owner_ids | array | – | Filter to these rental owner ids. |
| tenant_name | string | – | A current tenant's name contains this value. |
| unit_number | string | – | Unit number contains this value. |
No output schema declared.
No examples provided.
buildium_list_outstanding_balances List lease outstanding balances ~258
Delinquency report: leases that owe money, with aged buckets (0-30, 31-60, 61-90, 90+ days), total balance, past-due-email and eviction-pending dates. Leases with zero or credit balances are not returned. Buildium: GET /v1/leases/outstandingbalances.
| Name | Type | Req | Description |
|---|---|---|---|
| balance_duration | string | – | Only leases with a balance in this aging bucket. |
| entity_id | integer | – | Property or rental owner id (per entity_type). |
| entity_type | string | – | Scope by entity type; required with entity_id. |
| eviction_status | string | – | Eviction status. |
| lease_ids | array | – | Filter to these lease ids. |
| lease_statuses | array | – | Lease term statuses. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| past_due_email | string | – | Past-due email state. |
No output schema declared.
No examples provided.
buildium_list_rental_owners List rental owners ~245
List rental owners (the landlords you manage for) with contact details, management-agreement dates and the property ids they own. Buildium: GET /v1/rentals/owners.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_days_remaining | integer | – | Days remaining on the management agreement. |
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| owner_name | string | – | Owner name contains this value. |
| phone | string | – | Phone number contains this value. |
| property_ids | array | – | Filter to these property ids. |
| status | string | – | Owner status (both if omitted). |
No output schema declared.
No examples provided.
buildium_list_rental_properties List rental properties ~264
List rental properties (buildings) with address, unit count, type/subtype and manager. Filter by location (city/state contains), type, subtype, status, rental owner or property ids. Buildium: GET /v1/rentals.
| Name | Type | Req | Description |
|---|---|---|---|
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| location | string | – | City or state contains this value. |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| property_ids | array | – | Filter to these property ids. |
| rental_owner_ids | array | – | Filter to these rental owner ids. |
| status | string | – | Property status (both if omitted). |
| subtypes | array | – | Rental subtypes. |
| types | array | – | Rental types. |
No output schema declared.
No examples provided.
buildium_list_rental_units List rental units ~195
List rental units with unit number, bedrooms/bathrooms, size, market rent and whether each unit is listed or occupied. Filter by property. Buildium: GET /v1/rentals/units.
| Name | Type | Req | Description |
|---|---|---|---|
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| property_ids | array | – | Filter to these property ids. |
No output schema declared.
No examples provided.
buildium_list_tasks List tasks ~324
List all tasks/requests — contact requests, resident requests, rental owner requests and to-dos — with category, property, unit, requester, assignee, status, priority and due date. Buildium: GET /v1/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_id | integer | – | Assigned staff user id. |
| due_date_from | string | – | Due on or after — formatted YYYY-MM-DD. |
| due_date_to | string | – | Due on or before — formatted YYYY-MM-DD. |
| entity_id | integer | – | Entity id (per entity_type). |
| entity_type | string | – | Scope by entity type; required with entity_id. |
| last_updated_from | string | – | Updated on or after — formatted YYYY-MM-DD. |
| last_updated_to | string | – | Updated on or before — formatted YYYY-MM-DD. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| priorities | array | – | Priorities. |
| statuses | array | – | Task statuses. |
| task_category_id | integer | – | Task category id. |
| title | string | – | Title contains this value. |
| type | string | – | Task type. |
| unit_agreement_id | integer | – | Unit agreement (lease) id. |
| unit_id | integer | – | Unit id. |
No output schema declared.
No examples provided.
buildium_list_tenants List tenants ~305
List rental tenants with contact details, emergency contact, address and leases. Filter by name, email, phone, unit number, property, owner, unit ids or lease term status. Buildium: GET /v1/leases/tenants.
| Name | Type | Req | Description |
|---|---|---|---|
| building_statuses | array | – | Status of the tenant's property. |
| string | – | Email contains this value. | |
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| lease_term_statuses | array | – | Lease term statuses. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| name | string | – | Tenant name contains this value. |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| phone | string | – | Phone number contains this value. |
| property_ids | array | – | Filter to these property ids. |
| rental_owner_ids | array | – | Filter to these rental owner ids. |
| unit_ids | array | – | Filter to these unit ids. |
| unit_number | string | – | Unit number contains this value. |
No output schema declared.
No examples provided.
buildium_list_vendors List vendors ~255
List vendors (contractors, suppliers) with contact details, category, insurance and default expense GL account. Filter by name, email, phone, website, status or insurance expiration. Buildium: GET /v1/vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email contains this value. | |
| insurance_expiration | string | – | Insurance expiration window. |
| last_updated_from | string | – | Updated on or after — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| last_updated_to | string | – | Updated on or before — UTC, formatted YYYY-MM-DDTHH:MM:SSZ. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| name | string | – | Vendor name contains this value. |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| phone | string | – | Phone number contains this value. |
| status | string | – | Vendor status (both if omitted). |
| website | string | – | Website contains this value. |
No output schema declared.
No examples provided.
buildium_list_work_orders List work orders ~536
List work orders with title, status, priority, due date, vendor, amount, line items, linked task and bill ids. Filter by entity, status, priority, task type, unit, vendor, assignee, dates, amount, billed flag or title. Supply entity_type with entity_id (Rental for a property); statuses refer to the associated task. Dates must be YYYY-MM-DD, and each from value must be at most its to value. Buildium: GET /v1/workorders.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | number | – | Total amount at least this; must be at most amount_to when both are supplied. |
| amount_to | number | – | Total amount at most this; must be at least amount_from when both are supplied. |
| assigned_to_id | integer | – | The assigned staff user id (positive 32-bit integer). |
| due_date_from | string | – | Due on or after — formatted YYYY-MM-DD. |
| due_date_to | string | – | Due on or before — formatted YYYY-MM-DD. |
| entity_id | integer | – | The entity matching entity_type id (positive 32-bit integer). |
| entity_type | string | – | Scope by entity type; required with entity_id. |
| is_billed | boolean | – | Only work orders that do / do not have a bill. |
| last_updated_from | string | – | Updated on or after — formatted YYYY-MM-DD. |
| last_updated_to | string | – | Updated on or before — formatted YYYY-MM-DD. |
| limit | integer | – | Max results, 1-1000 (Buildium default 50). |
| offset | integer | – | Zero-based record offset for paging (default 0). |
| orderby | string | – | Sort, e.g. "Name", "LeaseToDate desc" or "Rent desc,City asc". Any field of the returned object. |
| priorities | array | – | Priorities. |
| statuses | array | – | Statuses of the associated task: New, InProgress, Completed, Deferred or Closed. |
| task_category_id | integer | – | The task category id (positive 32-bit integer). |
| task_ids | array | – | Filter to these task ids (positive 32-bit integers). |
| title | string | – | Title contains this value. |
| type | string | – | Type of the associated task. |
| unit_agreement_id | integer | – | The unit agreement (lease) id (positive 32-bit integer). |
| unit_id | integer | – | The unit id (positive 32-bit integer). |
| vendor_ids | array | – | Filter to these vendor ids (positive 32-bit integers). |
No output schema declared.
No examples provided.
buildium_update_todo_task Update a to-do task ~228
Update a to-do task — change status (e.g. mark Completed), priority, assignee, due date, title or category, optionally with an update message. Buildium's PUT replaces the whole record, so this reads the current task first and only changes the fields you pass. Buildium: GET then PUT /v1/tasks/todorequests/{toDoTaskId}.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_user_id | integer | – | Reassign to this staff user id. |
| category_id | integer | – | New task category id. |
| due_date | string | – | New due date, YYYY-MM-DD. |
| message | string | – | An update note recorded with this change. |
| priority | string | – | New priority. |
| property_id | integer | – | New active property id. |
| status | string | – | New status. |
| subcategory_id | integer | – | New task subcategory id. |
| title | string | – | New title (max 127). |
| todo_task_id | integer | yes | The to-do task id. |
| unit_id | integer | – | New unit id. |
No output schema declared.
No examples provided.
buildium_update_work_order Update a work order ~251
Update a work order's details. Buildium's PUT replaces the whole record, so this reads the current work order first and only changes the fields you pass — everything else (including line items and entry contacts) is preserved. Passing line_items REPLACES all existing line items. Status/priority/due date live on the linked task. Buildium: GET then PUT /v1/workorders/{workOrderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| chargeable_to | string | – | Who will be charged (max 100). |
| entry_allowed | string | – | Whether entry to the unit is allowed. |
| entry_contact_ids | array | – | Replace the entry contact user ids. |
| entry_notes | string | – | Notes on entering the unit. |
| invoice_number | string | – | Vendor invoice/reference number (max 50). |
| line_items | array | – | Replace ALL line items with this list. |
| title | string | – | New title (max 127). |
| vendor_id | integer | – | Reassign to this vendor id. |
| vendor_notes | string | – | Notes for the vendor. |
| work_details | string | – | New description of the work. |
| work_order_id | integer | yes | The work order id. |
No output schema declared.
No examples provided.
How do I install the Buildium MCP by usefulapi server?
Buildium MCP by usefulapi is a hosted endpoint at https://buildium.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 · buildium.usefulapi.io
claude mcp add --transport http io-usefulapi-buildium 'https://buildium.usefulapi.io/mcp'
What is the Buildium MCP by usefulapi server?
Buildium MCP by usefulapi is listed in the public MCP registry as io.usefulapi/buildium. Read Buildium properties, units, leases, tenants, balances and bills; manage work orders. This page covers its hosted endpoint (https://buildium.usefulapi.io/mcp).
Is the Buildium MCP by usefulapi server safe to use?
Buildium 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 Buildium MCP by usefulapi server expose?
Buildium MCP by usefulapi exposes 23 tools: buildium_list_rental_properties, buildium_get_rental_property, buildium_list_rental_units, buildium_get_rental_unit, buildium_list_rental_owners, and 18 more. Their descriptions and schemas cost roughly 5,102 tokens of context every time the server is loaded.
Does the Buildium MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Buildium 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 Buildium MCP by usefulapi server still maintained?
Buildium MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 22 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 Buildium MCP by usefulapi server?
VerifyMCP ran 4 checks on Buildium 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 Buildium 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.