Remote MCP · Endpoint

Ventis MCP server

No. Ventis answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://ventis.up.railway.app/mcp/pro

The last check completed an MCP handshake.

Registry name
io.github.Ops119/ventis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
295 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Crypto data for AI agents: prices, Solana wallets, token risk, swap quotes. Pay per call via x402.
Listing
From the official MCP registry (active).
Recent checks of Ventis
CheckedResultHandshake
39 minutes agoHandshake completed295 ms
3 days agoHandshake completed35 ms
13 days agoHandshake completed25 ms
13 days agoHandshake completed24 ms
15 days agoHandshake completed36 ms
16 days agoHandshake completed28 ms
17 days agoHandshake completed24 ms
18 days agoHandshake completed27 ms
18 days agoHandshake completed89 ms
20 days agoHandshake completed34 ms
22 days agoHandshake completed99 ms
25 days agoHandshake completed26 ms

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

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