Remote MCP · Endpoint
Nynch MCP Server MCP server
No. Nynch MCP Server answered an MCP handshake 42 minutes ago.
Up · key neededLast checked 42 minutes ago
Server URL
https://crcrwtjzqzinfzokianr.supabase.co/functions/v1/mcp-server
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.peterod99/nynch
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 286 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- CRM, relationship intelligence, and multi-agent orchestration for AI agents.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 42 minutes ago | Handshake completed | 286 ms |
| 3 hours ago | Handshake completed | 272 ms |
| 1 day ago | Handshake completed | 185 ms |
| 2 days ago | Handshake completed | 247 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 Nynch MCP Server and makes no claim about it beyond what these checks measured.