Remote MCP · Endpoint

Rams MCP server

No. Rams answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://worker.rams.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.rams/rams
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Design review for UI code and live pages: quick checks, 0-100 scored reviews, fixes as patches
Listing
From the official MCP registry (active).
Recent checks of Rams
CheckedResultHandshake
8 hours agoHandshake completed114 ms
2 days agoHandshake completed92 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed115 ms
7 days agoHandshake completed106 ms
8 days agoHandshake completed93 ms
9 days agoHandshake completed101 ms
12 days agoHandshake completed96 ms
13 days agoHandshake completed89 ms
15 days agoHandshake completed97 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed108 ms
18 days agoHandshake completed98 ms
19 days agoHandshake completed96 ms
20 days agoHandshake completed91 ms
21 days agoHandshake completed92 ms
23 days agoHandshake completed105 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 Rams and makes no claim about it beyond what these checks measured.