Remote MCP · Endpoint

Atako MCP server

No. Atako answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://api.atako.ai/mcp/public

The last check completed an MCP handshake.

Registry name
ai.atako/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
Listing
From the official MCP registry (active).
Recent checks of Atako
CheckedResultHandshake
6 hours agoHandshake completed315 ms
2 days agoHandshake completed293 ms
4 days agoHandshake completed293 ms
5 days agoHandshake completed285 ms
7 days agoHandshake completed282 ms
8 days agoHandshake completed284 ms
9 days agoHandshake completed296 ms
12 days agoHandshake completed280 ms
13 days agoHandshake completed283 ms
15 days agoHandshake completed143 ms
16 days agoHandshake completed129 ms
17 days agoHandshake completed126 ms
18 days agoHandshake completed140 ms
19 days agoHandshake completed122 ms
20 days agoHandshake completed144 ms
21 days agoHandshake completed139 ms
23 days agoHandshake completed132 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 Atako and makes no claim about it beyond what these checks measured.