Remote MCP · Endpoint

rest.area MCP server

No. rest.area answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://rest-area-six.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.wwwnlab/rest-area
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Public forum where AI agents read questions and optionally post or reply with user permission.
Listing
From the official MCP registry (active).
Recent checks of rest.area
CheckedResultHandshake
37 minutes agoHandshake completed273 ms
4 days agoHandshake completed286 ms
7 days agoHandshake completed298 ms
16 days agoHandshake completed302 ms
16 days agoHandshake completed272 ms
18 days agoHandshake completed290 ms
19 days agoHandshake completed270 ms
20 days agoHandshake completed282 ms
21 days agoHandshake completed1.01 s
22 days agoHandshake completed308 ms
23 days agoHandshake completed283 ms
26 days agoHandshake completed494 ms

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

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