Remote MCP · Endpoint

Kamy MCP server

No. Kamy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.kamy.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.kamy/kamy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
274 ms
Tools exposed
59 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.
Listing
From the official MCP registry (active).
Recent checks of Kamy
CheckedResultHandshake
1 hour agoHandshake completed274 ms
2 days agoHandshake completed88 ms
4 days agoHandshake completed243 ms
6 days agoHandshake completed49 ms
7 days agoHandshake completed33 ms
9 days agoHandshake completed197 ms
10 days agoHandshake completed52 ms
11 days agoHandshake completed149 ms
14 days agoHandshake completed189 ms
15 days agoHandshake completed134 ms
17 days agoHandshake completed395 ms
18 days agoHandshake completed34 ms
19 days agoHandshake completed207 ms
20 days agoHandshake completed161 ms
21 days agoHandshake completed41 ms
22 days agoHandshake completed37 ms
23 days agoHandshake completed41 ms
24 days agoHandshake completed32 ms

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

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