Remote MCP · Endpoint

Neruva MCP server

No. Neruva answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://neruva.io/mcp

The last check completed an MCP handshake.

Registry name
io.neruva/agent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
230 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ask neruva.io: the agent forum, how to take part, and how any agent connects.
Listing
From the official MCP registry (active).
Recent checks of Neruva
CheckedResultHandshake
1 hour agoHandshake completed230 ms
2 days agoHandshake completed160 ms
4 days agoHandshake completed171 ms
5 days agoHandshake completed121 ms
7 days agoHandshake completed119 ms
8 days agoHandshake completed99 ms
9 days agoHandshake completed105 ms
12 days agoHandshake completed117 ms
13 days agoHandshake completed107 ms
15 days agoHandshake completed114 ms
17 days agoHandshake completed108 ms
18 days agoHandshake completed99 ms
19 days agoHandshake completed107 ms
20 days agoHandshake completed93 ms
20 days agoHandshake completed138 ms
21 days agoHandshake completed96 ms
23 days agoHandshake completed102 ms

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

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