Remote MCP · Endpoint

PutRoots MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://www.putroots.com/mcp

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

Registry name
com.putroots/putroots
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
57.1% from 14 checks
Described by its publisher as
SF move agent: rentals with sources, no-SSN banking routes, and your move plan and drafts.
Website
https://www.putroots.com/connect
Listing
From the official MCP registry (active).
Recent checks of PutRoots
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
14 days agoHandshake completed29 ms
14 days agoHandshake completed48 ms
16 days agoHandshake completed24 ms
19 days agoHandshake completed30 ms
21 days agoHandshake completed31 ms
24 days agoHandshake completed25 ms
26 days agoHandshake completed26 ms
28 days agoHandshake completed24 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.