Remote MCP · Endpoint

com.costsegsmart/cost-seg-smart MCP server

No. com.costsegsmart/cost-seg-smart answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://costsegsmart.com/mcp

The last check completed an MCP handshake.

Registry name
com.costsegsmart/cost-seg-smart
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
207 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Cost segregation study pricing and Year-1 depreciation/tax-savings estimates for US properties.
Listing
From the official MCP registry (active).
Recent checks of com.costsegsmart/cost-seg-smart
CheckedResultHandshake
1 hour agoHandshake completed207 ms
2 days agoHandshake completed353 ms
4 days agoHandshake completed623 ms
5 days agoHandshake completed191 ms
7 days agoHandshake completed205 ms
7 days agoHandshake completed477 ms
9 days agoHandshake completed266 ms
12 days agoHandshake completed192 ms
13 days agoHandshake completed208 ms
15 days agoHandshake completed304 ms
16 days agoHandshake completed249 ms
17 days agoHandshake completed141 ms
18 days agoHandshake completed148 ms
19 days agoHandshake completed149 ms
20 days agoHandshake completed176 ms
21 days agoHandshake completed192 ms
22 days agoHandshake completed182 ms

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

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.costsegsmart/cost-seg-smart and makes no claim about it beyond what these checks measured.