Remote MCP · Endpoint

NeuralVerge MCP server

No. NeuralVerge answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://mcp.neuralverge.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.neuralverge/neuralverge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
517 ms
Tools exposed
364 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Structured, cited, real-world data from 300+ sources and the open web for your AI agents.
Listing
From the official MCP registry (active).
Recent checks of NeuralVerge
CheckedResultHandshake
42 minutes agoHandshake completed517 ms
3 days agoHandshake completed601 ms
13 days agoHandshake completed581 ms
13 days agoHandshake completed549 ms
15 days agoHandshake completed560 ms
15 days agoHandshake completed1.07 s
17 days agoHandshake completed424 ms
18 days agoHandshake completed434 ms
18 days agoHandshake completed521 ms
20 days agoHandshake completed525 ms
22 days agoHandshake completed483 ms
25 days agoHandshake completed492 ms
27 days agoHandshake completed455 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 NeuralVerge and makes no claim about it beyond what these checks measured.