Remote MCP · Endpoint

Canli Fundamentals MCP server

No. Canli Fundamentals answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://canlicapital.com/mcp/fundamentals

The last check completed an MCP handshake.

Registry name
io.github.arhancanli/canli-fundamentals-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
156 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
SEC fundamentals point in time: first reported, known as of a date, every restatement.
Listing
From the official MCP registry (active).
Recent checks of Canli Fundamentals
CheckedResultHandshake
20 minutes agoHandshake completed156 ms
3 days agoHandshake completed205 ms
14 days agoHandshake completed233 ms
14 days agoHandshake completed195 ms
15 days agoHandshake completed236 ms
16 days agoHandshake completed279 ms
18 days agoHandshake completed149 ms
18 days agoHandshake completed230 ms
19 days agoHandshake completed256 ms
21 days agoHandshake completed161 ms
23 days agoHandshake completed175 ms
25 days agoHandshake completed223 ms
28 days agoHandshake completed226 ms

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

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