Remote MCP · Endpoint

Ratevert MCP MCP server

No. Ratevert MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ratevert.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.ratevert/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
283 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only Ratevert MCP for asset search, pair rates, and conversions.
Listing
From the official MCP registry (active).
Recent checks of Ratevert MCP
CheckedResultHandshake
1 hour agoHandshake completed283 ms
2 days agoHandshake completed281 ms
4 days agoHandshake completed271 ms
5 days agoHandshake completed286 ms
7 days agoHandshake completed289 ms
8 days agoHandshake completed295 ms
9 days agoHandshake completed303 ms
12 days agoHandshake completed284 ms
13 days agoHandshake completed356 ms
15 days agoHandshake completed292 ms
16 days agoHandshake completed289 ms
17 days agoHandshake completed328 ms
18 days agoHandshake completed276 ms
19 days agoHandshake completed290 ms
20 days agoHandshake completed281 ms
21 days agoHandshake completed314 ms
22 days agoHandshake completed352 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 Ratevert MCP and makes no claim about it beyond what these checks measured.