Remote MCP · Endpoint

Kommo MCP server

No. Kommo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_kommo

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/kommo-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
118 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Kommo CRM (formerly amoCRM), the conversation-first sales CRM (WhatsApp, Instagram, Telegram) used b
Listing
From the official MCP registry (active).
Recent checks of Kommo
CheckedResultHandshake
1 hour agoHandshake completed118 ms
2 days agoHandshake completed113 ms
4 days agoHandshake completed135 ms
5 days agoHandshake completed927 ms
7 days agoHandshake completed157 ms
8 days agoHandshake completed258 ms
9 days agoHandshake completed50 ms
12 days agoHandshake completed74 ms
14 days agoHandshake completed58 ms
15 days agoHandshake completed141 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed193 ms
19 days agoHandshake completed151 ms
20 days agoHandshake completed347 ms
20 days agoHandshake completed116 ms
21 days agoHandshake completed41 ms
23 days agoHandshake completed90 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 Kommo and makes no claim about it beyond what these checks measured.