Remote MCP · Endpoint

com.depreo/site MCP server

No. com.depreo/site answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://depreo.com/mcp

The last check completed an MCP handshake.

Registry name
com.depreo/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
703 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Depreo: the site's own MCP server — dataset; every answer cites the site.
Listing
From the official MCP registry (active).
Recent checks of com.depreo/site
CheckedResultHandshake
1 hour agoHandshake completed703 ms
2 days agoHandshake completed1.05 s
4 days agoHandshake completed918 ms
5 days agoHandshake completed476 ms
7 days agoHandshake completed707 ms
8 days agoHandshake completed1.07 s
9 days agoHandshake completed741 ms
12 days agoHandshake completed704 ms
13 days agoHandshake completed976 ms
15 days agoHandshake completed904 ms
16 days agoHandshake completed684 ms
17 days agoHandshake completed512 ms
18 days agoHandshake completed779 ms
19 days agoHandshake completed758 ms
20 days agoHandshake completed511 ms
21 days agoHandshake completed448 ms
22 days agoHandshake completed356 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.depreo/site and makes no claim about it beyond what these checks measured.