Remote MCP · Endpoint

Refcat MCP server

No. Refcat answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.refcat.app/mcp

The last check completed an MCP handshake.

Registry name
app.refcat/refcat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
569 ms
Tools exposed
18 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Search 1M real UI flows and 3.3M screens from shipped apps, sites, emails and games.
Website
https://refcat.app/en/guides/mcp
Listing
From the official MCP registry (active).
Recent checks of Refcat
CheckedResultHandshake
2 hours agoHandshake completed569 ms
18 hours agoHandshake completed608 ms
2 days agoCredentials required—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Refcat and makes no claim about it beyond what these checks measured.