Remote MCP · Endpoint

Tenantback CAM Audit MCP server

No. Tenantback CAM Audit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tenantback.com/mcp

The last check completed an MCP handshake.

Registry name
com.tenantback/cam-audit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Audit a landlord's CAM reconciliation against the lease. Finds overcharges with clause citations.
Listing
From the official MCP registry (active).
Recent checks of Tenantback CAM Audit
CheckedResultHandshake
1 hour agoHandshake completed150 ms
9 days agoHandshake completed37 ms
10 days agoHandshake completed7.40 s
11 days agoHandshake completed34 ms
12 days agoHandshake completed28 ms
14 days agoHandshake completed7.22 s
14 days agoHandshake completed37 ms
15 days agoHandshake completed34 ms
17 days agoHandshake completed8.28 s
19 days agoHandshake completed42 ms
21 days agoHandshake completed38 ms
24 days agoHandshake completed54 ms
26 days agoHandshake completed41 ms
28 days agoHandshake completed41 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Tenantback CAM Audit and makes no claim about it beyond what these checks measured.