Remote MCP · Endpoint

Volanea MCP server

No. Volanea answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.volanea.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Pankaj-bit361/volanea
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
669 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Email infrastructure on Volanea: build templates, segments and workflows, send and check email.
Listing
From the official MCP registry (active).
Recent checks of Volanea
CheckedResultHandshake
1 hour agoHandshake completed669 ms
8 days agoHandshake completed833 ms
9 days agoHandshake completed650 ms
11 days agoHandshake completed633 ms
12 days agoHandshake completed642 ms
13 days agoHandshake completed638 ms
14 days agoHandshake completed693 ms
14 days agoHandshake completed699 ms
16 days agoHandshake completed797 ms
19 days agoHandshake completed667 ms
21 days agoHandshake completed731 ms
24 days agoHandshake completed647 ms
26 days agoHandshake completed323 ms
28 days agoHandshake completed1.18 s

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

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