Remote MCP · Endpoint

Recao MCP server

No. Recao answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://recao.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.recao/recao-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
264 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Rank a competitor's EU App Store ads by longevity. From Apple's official Ad Repository.
Listing
From the official MCP registry (active).
Recent checks of Recao
CheckedResultHandshake
1 hour agoHandshake completed264 ms
2 days agoHandshake completed84 ms
4 days agoHandshake completed110 ms
6 days agoHandshake completed81 ms
7 days agoHandshake completed107 ms
9 days agoHandshake completed73 ms
10 days agoHandshake completed79 ms
11 days agoHandshake completed87 ms
14 days agoHandshake completed104 ms
15 days agoHandshake completed71 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed69 ms
19 days agoHandshake completed66 ms
20 days agoHandshake completed86 ms
21 days agoHandshake completed70 ms
22 days agoHandshake completed68 ms
23 days agoHandshake completed82 ms
24 days agoHandshake completed92 ms

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

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