Remote MCP · Endpoint

Atly MCP server

No. Atly answered an MCP handshake 19 hours ago.

UpLast checked 19 hours ago

Server URL

https://agentic-api.atly.com/mcp

The last check completed an MCP handshake.

Registry name
com.atly/places
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
186 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find places by what you want (work friendly, gluten free, great coffee), scored from real reviews.
Listing
From the official MCP registry (active).
Recent checks of Atly
CheckedResultHandshake
19 hours agoHandshake completed186 ms
11 days agoHandshake completed194 ms
12 days agoHandshake completed152 ms
12 days agoHandshake completed244 ms
14 days agoHandshake completed132 ms
15 days agoHandshake completed145 ms
16 days agoHandshake completed1.04 s
17 days agoHandshake completed133 ms
18 days agoHandshake completed179 ms
20 days agoHandshake completed230 ms
22 days agoHandshake completed153 ms
25 days agoHandshake completed164 ms
27 days agoHandshake completed147 ms
29 days agoHandshake completed143 ms

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

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