io.usefulapi/buildium
REMOTE · BUILDIUM.USEFULAPI.IO · SCANNED OCT 4
Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4907 tokens (~213/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/buildium MCP server?
io.usefulapi/buildium 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'
{
"mcpServers": {
"io-usefulapi-buildium": {
"url": "https://buildium.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-buildium": {
"type": "http",
"url": "https://buildium.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-buildium] url = "https://buildium.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-buildium": {
"type": "remote",
"url": "https://buildium.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-buildium --url 'https://buildium.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-buildium:
url: "https://buildium.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-buildium": {
"Transport": "http",
"Url": "https://buildium.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-buildium -t streamable-http -u 'https://buildium.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-buildium": {
"type": "http",
"url": "https://buildium.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +3
- Authorization: fail → pass ▲ security
- 3 Oct 26 +39
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Server version: 1.0.0 → 1.5.1 functional
- 1 Oct 26 −36
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 30 Sept 26 +51
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
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 4 Oct 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 | 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 buildium.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://buildium.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://buildium.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://buildium.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://buildium.usefulapi.io/mcp |
| Authorisation server | https://buildium.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://buildium.usefulapi.io/mcp | HTTPS enforced | 301 | https://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 ~237
List vendor bills (accounts payable) with dates, memo, vendor, linked work order, reference number, approval status and lines. Read-only. Buildium: GET /v1/bills.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_statuses | array | – | Approval statuses. |
| entity_id | integer | – | Entity id with line items on the bill. |
| 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 | – | Vendor id. |
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 ~416
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. Buildium: GET /v1/workorders.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | number | – | Total amount at least this. |
| amount_to | number | – | Total amount at most this. |
| 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. |
| 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 | – | Work order statuses. |
| task_category_id | integer | – | Task category id. |
| task_ids | array | – | Filter to these task ids. |
| title | string | – | Title contains this value. |
| type | string | – | Type of the associated task. |
| unit_agreement_id | integer | – | Unit agreement (lease) id. |
| unit_id | integer | – | Unit id. |
| vendor_ids | array | – | Filter to these vendor ids. |
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.
What is the io.usefulapi/buildium MCP server?
io.usefulapi/buildium is an MCP server 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 io.usefulapi/buildium MCP server safe to use?
io.usefulapi/buildium scores 75 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 io.usefulapi/buildium MCP server expose?
io.usefulapi/buildium 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 4,907 tokens of context every time the server is loaded.
Does the io.usefulapi/buildium MCP server require authentication?
Yes. io.usefulapi/buildium asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/buildium MCP server still maintained?
io.usefulapi/buildium is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.