Remote MCP · Endpoint

Canarics MCP server

No. Canarics answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://canarics.com/mcp

The last check completed an MCP handshake.

Registry name
com.canarics/canarics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AI call analysis and voice agents for sales teams. Signup, usage, agents and call data over MCP.
Listing
From the official MCP registry (active).
Recent checks of Canarics
CheckedResultHandshake
1 hour agoHandshake completed303 ms
2 days agoHandshake completed174 ms
4 days agoHandshake completed312 ms
5 days agoHandshake completed313 ms
7 days agoHandshake completed238 ms
8 days agoHandshake completed304 ms
9 days agoHandshake completed185 ms
12 days agoHandshake completed320 ms
13 days agoHandshake completed184 ms
15 days agoHandshake completed195 ms
16 days agoHandshake completed308 ms
17 days agoHandshake completed189 ms
18 days agoHandshake completed186 ms
19 days agoHandshake completed182 ms
20 days agoHandshake completed187 ms
21 days agoHandshake completed298 ms
22 days agoHandshake completed297 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 Canarics and makes no claim about it beyond what these checks measured.