Remote MCP · Endpoint

NexIP MCP server

No. NexIP answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://nexip.ru/mcp

The last check completed an MCP handshake.

Registry name
ru.nexip/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
466 ms
Tools exposed
13 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Network, domain and website diagnostics for AI clients via MCP.
Website
https://nexip.ru/api/mcp
Listing
From the official MCP registry (active).
Recent checks of NexIP
CheckedResultHandshake
6 hours agoHandshake completed466 ms
9 days agoHandshake completed490 ms
10 days agoHandshake completed508 ms
11 days agoHandshake completed763 ms
12 days agoFailed - the connection was refused or dropped—
14 days agoHandshake completed480 ms
15 days agoHandshake completed474 ms
15 days agoHandshake completed502 ms
17 days agoHandshake completed486 ms
19 days agoHandshake completed484 ms
22 days agoHandshake completed640 ms
24 days agoHandshake completed459 ms
26 days agoHandshake completed477 ms
28 days agoHandshake completed462 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with NexIP and makes no claim about it beyond what these checks measured.