Remote MCP · Endpoint

Ncrypt MCP server

No. Ncrypt answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://ncrypt.me/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.andyrzr-bot/ncrypt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
316 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Share documents privately from an AI agent. The agent gets a link; it cannot read the file.
Listing
From the official MCP registry (active).
Recent checks of Ncrypt
CheckedResultHandshake
44 minutes agoHandshake completed316 ms
3 days agoHandshake completed338 ms
12 days agoHandshake completed305 ms
13 days agoHandshake completed328 ms
14 days agoHandshake completed331 ms
15 days agoHandshake completed1.94 s
16 days agoHandshake completed2.06 s
17 days agoHandshake completed1.54 s
18 days agoHandshake completed1.10 s
19 days agoHandshake completed419 ms
22 days agoHandshake completed407 ms
25 days agoHandshake completed1.05 s
27 days agoHandshake completed591 ms

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

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