Remote MCP · Endpoint

Curated MCP server

No. Curated answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://mcp.curated.network/

The last check completed an MCP handshake.

Registry name
network.curated/curated
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
50 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Keep and share lists of recommendations with your own notes, and read lists from people you trust.
Listing
From the official MCP registry (active).
Recent checks of Curated
CheckedResultHandshake
17 minutes agoHandshake completed101 ms
9 days agoHandshake completed129 ms
9 days agoHandshake completed103 ms
11 days agoHandshake completed106 ms
12 days agoHandshake completed135 ms
13 days agoHandshake completed112 ms
14 days agoHandshake completed202 ms
14 days agoHandshake completed129 ms
16 days agoHandshake completed116 ms
19 days agoHandshake completed107 ms
21 days agoHandshake completed115 ms
24 days agoHandshake completed134 ms
26 days agoHandshake completed106 ms
28 days agoHandshake completed108 ms

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

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