Skip to content

Buildium MCP by usefulapi

io.usefulapi/buildiumusefulapi.iostreamable-httpv1.46.5Scanned

Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.

23 tools: 4 can delete or cancel things and 19 only read.

Tools: 4 delete, 0 irreversible, 0 write, 19 read.
  • Reads private data · 6
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Buildium MCP by usefulapi can do

The Buildium MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 23 tools. It can delete or cancel things (4 tools: buildium_create_work_order, buildium_update_work_order, buildium_create_todo_task and buildium_update_todo_task). 19 tools only read.

6 tools read private data (buildium_list_rental_owners, buildium_list_outstanding_balances, buildium_list_tenants and 3 more); 1 tool brings in text other people can write (buildium_list_outstanding_balances).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.46.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

23 tools

Deletes or cancels 4Claude Code: deny
  • buildium_create_todo_taskCreate an internal to-do task assigned to a staff user, optionally tied to a property/unit and category, with a due date.No findings

    Why it is in this group

    • The name "buildium_create_todo_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a to-do task
    • destructiveHint: true
  • buildium_create_work_orderCreate a work order for a vendor.No findings

    Why it is in this group

    • The name "buildium_create_work_order" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a work order
    • destructiveHint: true
  • buildium_update_todo_taskUpdate a to-do task — change status (e.g.No findings

    Why it is in this group

    • The name "buildium_update_todo_task" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update a to-do task
    • destructiveHint: true
  • buildium_update_work_orderUpdate a work order's details.No findings

    Why it is in this group

    • The name "buildium_update_work_order" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update a work order
    • destructiveHint: true
Only reads 19Show 19 read-only tools
  • buildium_get_leaseFetch one lease by id, including tenants, cosigners, account details and move-out data.No findings

    Why it is in this group

    • The name "buildium_get_lease" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one lease by id, including tenants, cosigners, account details and move-out data. Buildium: GET /v1/leases/{leaseId}.

    Annotations the server declares

    • title: Get a lease
    • readOnlyHint: true
  • buildium_get_rental_propertyFetch one rental property by id.No findings

    Why it is in this group

    • The name "buildium_get_rental_property" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one rental property by id. Buildium: GET /v1/rentals/{propertyId}.

    Annotations the server declares

    • title: Get a rental property
    • readOnlyHint: true
  • buildium_get_rental_unitFetch one rental unit by id.No findings

    Why it is in this group

    • The name "buildium_get_rental_unit" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one rental unit by id. Buildium: GET /v1/rentals/units/{unitId}.

    Annotations the server declares

    • title: Get a rental unit
    • readOnlyHint: true
  • buildium_get_tenantFetch one rental tenant by id.No findings

    Why it is in this group

    • The name "buildium_get_tenant" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one rental tenant by id. Buildium: GET /v1/leases/tenants/{tenantId}.

    Annotations the server declares

    • title: Get a tenant
    • readOnlyHint: true
  • buildium_get_work_orderFetch one work order by id.No findings

    Why it is in this group

    • The name "buildium_get_work_order" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one work order by id. Buildium: GET /v1/workorders/{workOrderId}.

    Annotations the server declares

    • title: Get a work order
    • readOnlyHint: true
  • buildium_list_applicantsList rental applicants with contact details, status and their applications.Reads private dataNo findings

    Why it is in this group

    • The name "buildium_list_applicants" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List applicants
    • readOnlyHint: true
  • buildium_list_associationsList community/HOA associations with address, manager, reserve, fiscal year and operating bank account.No findings

    Why it is in this group

    • The name "buildium_list_associations" says "list": a word for reading.
    Description, as the server wrote it
    List community/HOA associations with address, manager, reserve, fiscal year and operating bank account. Buildium: GET /v1/associations.

    Annotations the server declares

    • title: List associations
    • readOnlyHint: true
  • buildium_list_billsList vendor bills (accounts payable) with dates, memo, vendor, linked work order, reference number, approval status and lines.No findings

    Why it is in this group

    • The name "buildium_list_bills" says "list": a word for reading.
    Description, as the server wrote it
    List vendor bills (accounts payable) with dates, memo, vendor, linked work order, reference number, approval status and lines. Read-only. Buildium: GET /v1/bills.

    Annotations the server declares

    • title: List bills
    • readOnlyHint: true
  • buildium_list_gl_accountsList the chart of accounts: GL accounts with number, name, type/subtype, sub-accounts and bank/credit-card flags.No findings

    Why it is in this group

    • The name "buildium_list_gl_accounts" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List general ledger accounts
    • readOnlyHint: true
  • buildium_list_lease_transactionsRead a lease's ledger: charges, payments, credits, refunds, deposits and other transactions with date, type, total amount and journal lines.No findings

    Why it is in this group

    • The name "buildium_list_lease_transactions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List lease transactions
    • readOnlyHint: true
  • buildium_list_leasesList leases with unit, dates, lease type/status, current tenants, rent/deposit account details and eviction flag.No findings

    Why it is in this group

    • The name "buildium_list_leases" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List leases
    • readOnlyHint: true
  • buildium_list_outstanding_balancesDelinquency 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "buildium_list_outstanding_balances" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List lease outstanding balances
    • readOnlyHint: true
  • buildium_list_rental_ownersList rental owners (the landlords you manage for) with contact details, management-agreement dates and the property ids they own.Reads private dataNo findings

    Why it is in this group

    • The name "buildium_list_rental_owners" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List rental owners
    • readOnlyHint: true
  • buildium_list_rental_propertiesList rental properties (buildings) with address, unit count, type/subtype and manager.No findings

    Why it is in this group

    • The name "buildium_list_rental_properties" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List rental properties
    • readOnlyHint: true
  • buildium_list_rental_unitsList rental units with unit number, bedrooms/bathrooms, size, market rent and whether each unit is listed or occupied.No findings

    Why it is in this group

    • The name "buildium_list_rental_units" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List rental units
    • readOnlyHint: true
  • buildium_list_tasksList all tasks/requests — contact requests, resident requests, rental owner requests and to-dos — with category, property, unit, requester, assignee, status, priority and due date.Reads private dataNo findings

    Why it is in this group

    • The name "buildium_list_tasks" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true
  • buildium_list_tenantsList rental tenants with contact details, emergency contact, address and leases.Reads private dataNo findings

    Why it is in this group

    • The name "buildium_list_tenants" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List tenants
    • readOnlyHint: true
  • buildium_list_vendorsList vendors (contractors, suppliers) with contact details, category, insurance and default expense GL account.Reads private dataNo findings

    Why it is in this group

    • The name "buildium_list_vendors" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List vendors
    • readOnlyHint: true
  • buildium_list_work_ordersList work orders with title, status, priority, due date, vendor, amount, line items, linked task and bill ids.No findings

    Why it is in this group

    • The name "buildium_list_work_orders" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List work orders
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:33 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://buildium.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://buildium.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://buildium.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://buildium.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.46.5. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__buildium__buildium_list_rental_properties",
      "mcp__buildium__buildium_get_rental_property",
      "mcp__buildium__buildium_list_rental_units",
      "mcp__buildium__buildium_get_rental_unit",
      "mcp__buildium__buildium_list_rental_owners",
      "mcp__buildium__buildium_list_leases",
      "mcp__buildium__buildium_get_lease",
      "mcp__buildium__buildium_list_outstanding_balances",
      "mcp__buildium__buildium_list_lease_transactions",
      "mcp__buildium__buildium_list_tenants",
      "mcp__buildium__buildium_get_tenant",
      "mcp__buildium__buildium_list_applicants",
      "mcp__buildium__buildium_list_work_orders",
      "mcp__buildium__buildium_get_work_order",
      "mcp__buildium__buildium_list_tasks",
      "mcp__buildium__buildium_list_vendors",
      "mcp__buildium__buildium_list_bills",
      "mcp__buildium__buildium_list_gl_accounts",
      "mcp__buildium__buildium_list_associations"
    ],
    "ask": [],
    "deny": [
      "mcp__buildium__buildium_create_work_order",
      "mcp__buildium__buildium_update_work_order",
      "mcp__buildium__buildium_create_todo_task",
      "mcp__buildium__buildium_update_todo_task"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as buildium. Review it before you use it.

Capability tags behind 6 rules
  • mcp__buildium__buildium_list_rental_owners private-data
  • mcp__buildium__buildium_list_outstanding_balances private-data, untrusted-input
  • mcp__buildium__buildium_list_tenants private-data
  • mcp__buildium__buildium_list_applicants private-data
  • mcp__buildium__buildium_list_tasks private-data
  • mcp__buildium__buildium_list_vendors private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/buildium/verify?hash=d8f07ec5da53bce2ddad0552006de95fc21dbcd459c3aab6ceb1c277492fa4c9" | jq -e '.changed == false'

Pinned hash d8f07ec5da53, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/buildium/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/buildium
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/buildium.svg)](https://radar.anlyon.com/servers/io.usefulapi/buildium)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Buildium MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Buildium MCP by usefulapi safe?

No scan can promise that. What its definitions show: 23 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Buildium MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: buildium_create_work_order, buildium_update_work_order, buildium_create_todo_task and buildium_update_todo_task.

Can the Buildium MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Buildium MCP by usefulapi have?

23 tools: 4 destructive, 19 read. buildium_create_work_order, buildium_update_work_order, buildium_create_todo_task, buildium_update_todo_task, buildium_list_rental_properties, buildium_get_rental_property, buildium_list_rental_units, buildium_get_rental_unit and 15 more.

Does the Buildium MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Buildium MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Buildium MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.