Remote MCP · Endpoint

Waply for Kommo MCP server

No. Waply for Kommo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://waply.online/mcp

The last check completed an MCP handshake.

Registry name
online.waply/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
271 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Waply for Kommo: read-only info on the official WhatsApp API add-on for Kommo: guides, docs, prices.
Listing
From the official MCP registry (active).
Recent checks of Waply for Kommo
CheckedResultHandshake
1 hour agoHandshake completed271 ms
9 days agoHandshake completed409 ms
10 days agoHandshake completed588 ms
11 days agoHandshake completed194 ms
12 days agoHandshake completed190 ms
14 days agoHandshake completed240 ms
14 days agoHandshake completed215 ms
15 days agoHandshake completed220 ms
17 days agoHandshake completed268 ms
19 days agoHandshake completed209 ms
21 days agoHandshake completed306 ms
24 days agoHandshake completed250 ms
26 days agoHandshake completed266 ms
28 days agoHandshake completed236 ms

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

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