Remote MCP · Endpoint

Canli Validation MCP server

No. Canli Validation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
215 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed215 ms
2 days agoHandshake completed302 ms
4 days agoHandshake completed208 ms
6 days agoHandshake completed160 ms
8 days agoHandshake completed155 ms
10 days agoHandshake completed168 ms
12 days agoHandshake completed157 ms
13 days agoHandshake completed285 ms
14 days agoHandshake completed154 ms
15 days agoHandshake completed164 ms
18 days agoHandshake completed289 ms
19 days agoHandshake completed181 ms
21 days agoHandshake completed159 ms
23 days agoHandshake completed185 ms
24 days agoHandshake completed330 ms

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

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.