Remote MCP · Endpoint

NeuralVerge MCP server

No. NeuralVerge answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://api.neuralverge.ai/functions/v1/mcp-server

The last check completed an MCP handshake.

Registry name
ai.neuralverge/neuralverge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
938 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
18 minutes agoHandshake completed938 ms
9 days agoHandshake completed638 ms
9 days agoHandshake completed638 ms
11 days agoHandshake completed621 ms
12 days agoHandshake completed534 ms
13 days agoHandshake completed470 ms
14 days agoHandshake completed642 ms
14 days agoHandshake completed438 ms
16 days agoHandshake completed535 ms
19 days agoHandshake completed666 ms
21 days agoHandshake completed497 ms
24 days agoHandshake completed536 ms
26 days agoHandshake completed546 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.