Remote MCP · Endpoint

Buildium MCP by usefulapi MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://buildium.usefulapi.io/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.usefulapi/buildium
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
23 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.
Listing
From the official MCP registry (active).
Recent checks of Buildium MCP by usefulapi
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed410 ms
4 days agoHandshake completed187 ms
6 days agoHandshake completed308 ms
8 days agoHandshake completed322 ms
10 days agoHandshake completed357 ms
12 days agoHandshake completed197 ms
14 days agoHandshake completed179 ms
15 days agoHandshake completed209 ms
16 days agoHandshake completed370 ms
18 days agoHandshake completed200 ms
20 days agoHandshake completed266 ms
22 days agoHandshake completed194 ms
23 days agoHandshake completed207 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Buildium MCP by usefulapi and makes no claim about it beyond what these checks measured.