Remote MCP · Endpoint

Canonsheet MCP server

No. Canonsheet answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://canonsheet.kaneky.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kaneky/canonsheet
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
485 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Consistent prompts for one human character across image and video models. Paid per call, x402.
Listing
From the official MCP registry (active).
Recent checks of Canonsheet
CheckedResultHandshake
1 hour agoHandshake completed485 ms
9 days agoHandshake completed441 ms
10 days agoHandshake completed474 ms
11 days agoHandshake completed434 ms
12 days agoHandshake completed411 ms
14 days agoHandshake completed417 ms
14 days agoHandshake completed173 ms
15 days agoHandshake completed442 ms
17 days agoHandshake completed398 ms
19 days agoHandshake completed424 ms
21 days agoHandshake completed424 ms
24 days agoHandshake completed460 ms
26 days agoHandshake completed417 ms
28 days agoHandshake completed212 ms

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

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