Remote MCP · Endpoint

FrelyMCP MCP server

No. FrelyMCP answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://mcp.frely.cloud/mcp/public

The last check completed an MCP handshake.

Registry name
cloud.frely/frelymcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
344 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Use your own computers, cloud tools and AI agents from any MCP client with one Frely login.
Listing
From the official MCP registry (active).
Recent checks of FrelyMCP
CheckedResultHandshake
19 minutes agoHandshake completed344 ms
9 days agoHandshake completed358 ms
9 days agoHandshake completed464 ms
11 days agoHandshake completed378 ms
12 days agoHandshake completed485 ms
13 days agoHandshake completed352 ms
14 days agoHandshake completed367 ms
14 days agoHandshake completed352 ms
16 days agoHandshake completed147 ms
19 days agoHandshake completed435 ms
21 days agoHandshake completed353 ms
24 days agoHandshake completed325 ms
26 days agoHandshake completed496 ms

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

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