Remote MCP · Endpoint

com.esti-maite/construction-takeoff-estimating MCP server

No. com.esti-maite/construction-takeoff-estimating answered an MCP handshake 53 minutes ago.

Up · key neededLast checked 53 minutes ago

Server URL

https://mcp.esti-maite.com/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.esti-maite/construction-takeoff-estimating
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
Behind credentials
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Construction takeoff and estimating for AI agents. Measure a drawing PDF, export a priced estimate.
Listing
From the official MCP registry (active).
Recent checks of com.esti-maite/construction-takeoff-estimating
CheckedResultHandshake
53 minutes agoHandshake completed77 ms
1 day agoHandshake completed68 ms
2 days agoHandshake completed69 ms

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

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 com.esti-maite/construction-takeoff-estimating and makes no claim about it beyond what these checks measured.