Remote MCP · Endpoint

PutRoots MCP server

No. PutRoots answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.putroots.com/mcp

The last check completed an MCP handshake.

Registry name
com.putroots/putroots
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
24 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
SF move agent: rentals with sources, no-SSN banking routes, and your move plan and drafts.
Listing
From the official MCP registry (active).
Recent checks of PutRoots
CheckedResultHandshake
2 hours agoHandshake completed24 ms
2 days agoHandshake completed54 ms
4 days agoHandshake completed21 ms
6 days agoHandshake completed22 ms
7 days agoHandshake completed23 ms
9 days agoHandshake completed40 ms
10 days agoHandshake completed27 ms
11 days agoHandshake completed27 ms
14 days agoHandshake completed23 ms
15 days agoHandshake completed24 ms
17 days agoHandshake completed47 ms
19 days agoHandshake completed22 ms
20 days agoHandshake completed23 ms
21 days agoHandshake completed24 ms
22 days agoHandshake completed59 ms
22 days agoHandshake completed59 ms

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

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 PutRoots and makes no claim about it beyond what these checks measured.