Remote MCP · Endpoint

Canli Validation MCP server

No. Canli Validation answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://canlicapital.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.arhancanli/canli-validation-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
182 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Deflated Sharpe and PBO checks. A verdict is not admission to anything and is not a forecast.
Listing
From the official MCP registry (active).
Recent checks of Canli Validation
CheckedResultHandshake
53 minutes agoHandshake completed182 ms
3 days agoHandshake completed160 ms
12 days agoHandshake completed220 ms
13 days agoHandshake completed237 ms
14 days agoHandshake completed179 ms
15 days agoHandshake completed181 ms
17 days agoHandshake completed262 ms
18 days agoHandshake completed155 ms
18 days agoHandshake completed247 ms
20 days agoHandshake completed194 ms
22 days agoHandshake completed190 ms
25 days agoHandshake completed189 ms
27 days agoHandshake completed215 ms
29 days agoHandshake completed302 ms

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

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